# Update Stage

`Update_Stage` updates an existing GovTribe stage and returns the updated stage resource as JSON text.

## Output Contract

* Top-level keys:
  * `govtribe_id`
  * `govtribe_type`
  * `govtribe_url`
  * `name`
  * `description`
  * `type`
  * `created_at`
  * `updated_at`
  * `owner`
  * `creator`
  * `pipeline`
* Row keys:
  * `n/a`
* Relationship retrieval map:
  * `creator`
    * `resource_type`: `user`
    * `tool`: `Search_Users`
    * `filter`: `user_ids`
    * `nested_keys`: `govtribe_id`, `govtribe_type`, `name`, `email`
  * `owner`
    * `resource_type`: `user`
    * `tool`: `Search_Users`
    * `filter`: `user_ids`
    * `nested_keys`: `govtribe_id`, `govtribe_type`, `name`, `email`
  * `pipeline`
    * `resource_type`: `pipeline`
    * `tool`: `Search_Pipelines`
    * `filter`: `creator_ids`
    * `nested_keys`: `govtribe_id`, `govtribe_type`, `govtribe_url`, `name`

## Usage Patterns

Pattern A: Rename and reposition a stage in the pipeline sequence. Tool: `Update_Stage`

```json
{
  "stage_id": "<STAGE_ID>",
  "name": "Proposal Review",
  "index": 4
}
```

Pattern B: Update stage description while keeping current order. Tool: `Update_Stage`

```json
{
  "stage_id": "<STAGE_ID>",
  "description": "Gate for final compliance, pricing, and approval checks before submission."
}
```

Pattern C: Reorder pursuits inside a stage lane after pipeline review. Tool: `Update_Stage`

```json
{
  "stage_id": "<STAGE_ID>",
  "pursuit_index_map": [
    {
      "_id": "<PURSUIT_ID_1>",
      "index": 0
    },
    {
      "_id": "<PURSUIT_ID_2>",
      "index": 1
    }
  ]
}
```

Pattern D: Apply metadata updates and pursuit reordering in one idempotent request. Tool: `Update_Stage`

```json
{
  "stage_id": "<STAGE_ID>",
  "name": "Ready to Submit",
  "description": "Final stage before proposal handoff and release.",
  "index": 5,
  "pursuit_index_map": [
    {
      "_id": "<PURSUIT_ID_3>",
      "index": 0
    },
    {
      "_id": "<PURSUIT_ID_4>",
      "index": 1
    }
  ]
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.govtribe.com/user-guide/mcp/tools/update-stage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.