Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Project Membership

delete_project_membership
DestructiveIdempotent

Delete a project membership for a reference user in Procore. Permanently removes the association using project, membership, and party IDs; verify IDs with the list tool first to avoid errors.

Instructions

Delete a Project Membership for a party on the given Project. This endpoint can currently only be used to delete reference users from a project. It cannot be used to delete a user who has a login or to delete vendors. Confirm the target id with the matching show or list tool before calling. 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. Permanently removes the project membership. This cannot be undone, and a repeat call returns 404. 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, party_id. Procore API: Core > Directory. Endpoint: DELETE /rest/v1.0/projects/{project_id}/project_memberships/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — the ID of the Project Membership
party_idYesQuery string parameter — the ID of the Party (reference user)
project_idYesURL path parameter — unique identifier for the project.
Behavior5/5

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

Beyond the existing annotations (destructive, idempotent), the description adds critical behavioral details: permanence, a repeat call returning 404, common error statuses (401/403/404), and the restriction to reference users. This enriches the agent's understanding of side effects and failure modes.

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 every sentence contributes useful information, front-loading the core purpose and then covering scope, preconditions, consequences, and errors. It is long due to the destructive nature of the tool, but could be slightly tightened without losing value.

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

Completeness4/5

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

The description covers purpose, constraints, preconditions, side effects, default behavior, and error handling. It does not describe the success response, which is typically implicit for a delete operation, but the overall context is highly complete for safe invocation.

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

Parameters4/5

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

Schema descriptions already cover all three parameters with 100% coverage, but the description adds valuable semantics: project_id defaults to the configured value when omitted, and id must be resolved via a list tool. This goes beyond simple parameter 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 a specific verb and resource ('Delete a Project Membership for a party on the given Project'), then explicitly distinguishes its scope by stating it only applies to reference users and cannot delete login users or vendors. This distinguishes it from related membership tools.

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

Usage Guidelines5/5

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

It clearly states when the tool cannot be used (login users, vendors), instructs the agent to confirm the target id with a show or list tool first, and explains the project_id defaulting behavior. This provides explicit when-to-use and when-not-to-use guidance.

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