Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete The Project Logo

delete_the_project_logo
DestructiveIdempotent

Permanently removes a project's logo using the project ID. This action cannot be undone.

Instructions

Updates the project setting the logo reference to null. Use this to permanently delete the specified Portfolio records. This cannot be undone. Permanently removes the specified Portfolio records. This action cannot be undone. Required parameters: id. Procore API: Core > Portfolio. Endpoint: DELETE /rest/v1.0/projects/{id}/logo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier for the project.
Behavior2/5

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

Annotations provide destructiveHint=true, which aligns with the permanent deletion stated, but the description erroneously references Portfolio records, undermining trust. It adds that it cannot be undone, but the error reduces transparency.

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 repeats 'This cannot be undone' and 'Permanently removes the specified Portfolio records' twice each. It is verbose and includes irrelevant Portfolio text, making it inefficient.

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?

The description does not mention the response or side effects beyond deletion. The inclusion of Portfolio records distracts from the actual tool purpose, leaving gaps for an agent.

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?

Schema coverage is 100% with a clear description of the 'id' parameter. The description merely restates that 'id' is required, adding no extra semantic value 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 tool name and title clearly indicate deleting the project logo, but the description confuses by mentioning 'permanently delete the specified Portfolio records,' which is inconsistent and likely a copy-paste error. The verb 'updates' also softens the delete action.

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

Usage Guidelines1/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 versus alternatives. The description incorrectly states it deletes Portfolio records, providing no useful contextual direction for an agent.

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