Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get Or Create Document Info

get_or_create_document_info

Fetch or create a document in Procore and get only essential document details for UI, with default company and project from config.

Instructions

Get or create a document and return only essential document information for UI. company_id and project_id default to the values set by procore_set_config when omitted. Acts on the or create document info and returns Procore's response for the operation. 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: company_id, project_id, item_id, item_type. Procore API (v2.0): Project Management > Document Markup. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/viewer_documents/get_or_create

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesJSON request body field — unique identifier of the item
item_typeYesJSON request body field — the item type for this Document Markup operation
company_idYesURL path parameter — unique identifier of the company
project_idYesURL path parameter — unique identifier of the project
attachment_idNoJSON request body field — unique identifier of the attachment
attachment_sourceNoJSON request body field — the attachment source for this Document Markup operation
internal_pdm_tool_dataNoJSON request body field — internal_pdm_tool_data
Behavior4/5

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

Annotations already indicate read/write traits. The description adds useful behavioral context: default values for company/project from config, and error payloads with HTTP status codes (401/403/404) indicating auth and permission requirements. No contradiction.

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

Conciseness3/5

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

The description includes purpose, defaults, error handling, and API info, but contains a grammatically awkward redundant sentence ('Acts on the or create document info...') and repeats the required parameters list already in schema.

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?

Without an output schema, the description partially explains the return value ('essential document information') and covers defaults, errors, and endpoint. It does not provide detailed return structure, but the description is sufficiently complete for an operation tool with annotations.

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 covers all 7 params with descriptions (100% coverage). The description adds default behavior for company_id/project_id but otherwise repeats required parameters and doesn't elaborate on remaining params beyond schema.

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

Purpose4/5

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

The description clearly states the tool gets or creates a document and returns essential info for UI. It names the verb and resource, but does not explicitly distinguish from sibling tools like show_or_create_document_markup_downloadable_pdf.

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

Usage Guidelines3/5

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

Provides context that company_id/project_id default from procore_set_config, and mentions common error statuses, but does not explicitly state when to use this tool over alternatives or when not to use it.

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