Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Link

show_link
Read-onlyIdempotent

Retrieve full details of a specific Project-Level Configuration record by its ID and project ID. Returns a JSON object with the requested project link information.

Instructions

Show detailed information for a specific Project Home Link. Use this to fetch the full details of a specific Project-Level Configuration records by its identifier. Returns a JSON object describing the requested Project-Level Configuration records. Required parameters: project_id, id. Procore API: Company Admin > Project-Level Configuration. Endpoint: GET /rest/v1.0/links/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Project-Level Configuration resource
project_idYesQuery string parameter — unique identifier for the project.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already cover readOnly and idempotent hints; description adds endpoint and return type but no new behavioral context.

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?

Mostly concise but includes redundant phrases like 'Show...' followed by 'Use this to fetch...' that could be merged.

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

Completeness3/5

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

No output schema; description only says 'returns a JSON object' without detailing shape or pagination info for optional params.

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%; description merely repeats required parameters without adding new meaning.

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 clearly states it shows detailed information for a specific Project Home Link, distinguishing it from list and update tools among siblings.

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?

Explicitly instructs to use for fetching full details by identifier, but does not mention when not to use or provide explicit alternatives.

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