Skip to main content
Glama
TylerIlunga

Procore MCP Server

Remove A Response From An Item Response Set

remove_a_response_from_an_item_response_set
DestructiveIdempotent

Permanently delete a response from a checklist item response set. This action cannot be undone.

Instructions

Remove a Response from an Item Response Set. Use this to permanently delete the specified Inspections. This cannot be undone. Permanently removes the specified Inspections. This action cannot be undone. Required parameters: company_id, response_set_id, id. Procore API: Project Management > Inspections. Endpoint: DELETE /rest/v1.0/companies/{company_id}/checklist/item/response_sets/{response_set_id}/responses/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
response_set_idYesURL path parameter — checklist Item Response Set ID
idYesURL path parameter — the ID of the Response
Behavior1/5

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

The description inaccurately claims the tool deletes 'Inspections' instead of 'Responses', which is misleading about the behavior. Although annotations already indicate destructiveHint=true, the description adds no useful behavioral context beyond irreversibility, and the factual error undermines trust.

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

Conciseness2/5

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

The description is repetitive: 'permanently delete the specified Inspections' and 'This cannot be undone' appear twice. It includes an endpoint path that may be extraneous. Multiple sentences waste space without adding value.

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

Completeness1/5

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

The description is inaccurate (references Inspections instead of Responses) and lacks details about consequences of deletion, such as impact on the response set or permission requirements. Given the error and missing context, it fails to provide a complete understanding of the tool.

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?

The input schema has 3 parameters, each with descriptions (100% coverage). The description lists required parameters but does not add meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 description states 'Remove a Response from an Item Response Set' but then erroneously says 'permanently delete the specified Inspections'. This misidentifies the resource and creates confusion. The title and tool name are clear, but the description directly contradicts the actual operation.

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?

The description says 'Use this to permanently delete the specified Inspections' and emphasizes irreversibility, but it does not differentiate from sibling tools like 'delete_a_response' or 'add_an_existing_response_to_an_item_response_set'. No guidance on when to use this versus alternatives is provided.

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