Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update A Crew

update_a_crew
Idempotent

Update a crew for a Procore project by providing the project and crew IDs. Send only the fields you want to change; omitted fields stay unchanged.

Instructions

Updating a Crew associated with the specified Project. Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "crew" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified crew on success. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id, id. Procore API: Core > Directory. Endpoint: PATCH /rest/v1.0/projects/{project_id}/crews/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Directory resource
nameNoJSON request body field — crew Name
party_idsNoJSON request body field — array of party identifiers
project_idYesURL path parameter — unique identifier for the project.
equipment_idsNoJSON request body field — array of equipment identifiers
lead_party_idNoJSON request body field — party Id of crew leader
Behavior5/5

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

Beyond annotations, the description discloses partial-update behavior, project_id defaulting, return value, and specific error statuses (401/403/404). This adds significant context to the readOnlyHint=false and idempotentHint=true annotations without contradiction.

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

Conciseness4/5

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

The description is dense but well-structured. Every sentence provides value, but the error-handling section could be trimmed for brevity without losing essential info.

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

Completeness5/5

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

Covers operation, parameters, defaults, error handling, return value, and API endpoint. No output schema exists, so this description fully compensates.

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

Parameters5/5

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

Though schema covers all parameters, the description adds crucial semantics: fields are nested under 'crew' in the payload, project_id defaults to config, and id must reference an existing record. This goes beyond property descriptions.

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

Purpose5/5

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

The description opens with 'Updating a Crew associated with the specified Project,' clearly identifying the action (update), resource (crew), and scope (project). It distinguishes itself from sibling create/delete/list crew tools by the verb and mentions the PATCH endpoint.

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

Usage Guidelines4/5

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

Provides explicit usage guidance: partial update semantics, omitting fields preserves values, project_id default behavior, and resolving id with the list tool first. However, it doesn't explicitly exclude creation or other scenarios, so not a 5.

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