Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Project Stage

update_project_stage

Update an existing project stage in Procore by providing its ID and company ID. Modify fields such as name, category, or bidding stage status.

Instructions

Update the specified Project Stage. Use this to update an existing Company Settings (only the supplied fields are changed). Updates the specified Company Settings and returns the modified object on success. Required parameters: company_id, id. Procore API: Company Admin > Company Settings. Endpoint: PATCH /rest/v1.0/companies/{company_id}/project_stages/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — iD of the project stage
is_bidding_stageNoJSON request body field — the Bidding Stage status of the Project Stage
nameNoJSON request body field — the Name of the Project Stage
categoryNoJSON request body field — the Category Type of the Project Stage
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate a write operation (readOnlyHint=false). The description adds that it returns the modified object, but the contradictory mention of 'Company Settings' undermines trust. No disclosure of side effects or authorization needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but contains unnecessary and incorrect information ('Company Settings'). It could be streamlined by removing the error and focusing on the project stage context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description only vaguely states 'returns the modified object.' Lacks details on return format or error scenarios. The error further reduces completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers all parameters (100% coverage). The description redundantly lists required parameters and repeats the API endpoint but adds no meaningful semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'update' is clear, but the description claims it updates 'an existing Company Settings' which contradicts the tool name 'update_project_stage' and the input schema. This inconsistency makes the purpose ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs. alternatives like create_project_stage or delete_project_stage. The description does not differentiate from sibling tools or specify prerequisites beyond required parameters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TylerIlunga/procore-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server