Skip to main content
Glama
TylerIlunga

Procore MCP Server

Generates PDF Document

generates_pdf_document

Generate a PDF document listing project users, with filters for permission template, vendor, and trade, and options to include contacts, vendors, or user roles, and group by vendor.

Instructions

Generate PDF Document from a project. The endpoint returns url to PDF file. See Filtering on List Actions for information on using the filtering capabilities provided by this endpoint. Use this to perform the generates pdf action on Directory records. Generates the export and returns a download URL or async job handle. Required parameters: project_id. Procore API: Core > Directory. Endpoint: POST /rest/v1.0/projects/{project_id}/users/pdf

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
filters__permission_templateNoQuery string parameter — permission Template ID. Returns item(s) assiociated with the specified Permission Template ID.
filters__vendor_idNoQuery string parameter — return item(s) with the specified Vendor IDs.
filters__idNoQuery string parameter — returns users whose id attribute matches the parameter.
filters__except_idNoQuery string parameter — returns users except as specified.
filters__trade_id__NoQuery string parameter — returns users whose vendor record is associated with the specified trade id(s).
contactNoQuery string parameter — indicates whether contacts should be included in PDF document.
vendorNoQuery string parameter — indicates whether vendor should be included in PDF document.
user_roleNoQuery string parameter — indicates whether user_role should be included in PDF document.
grouped_by_vendorNoQuery string parameter — indicates whether users should be grouped by vendor.
Behavior4/5

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

The description adds value beyond annotations by disclosing that the tool returns either a download URL or an async job handle, implying asynchronous behavior. Annotations provide no such detail, and there is 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.

Conciseness2/5

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

The description is verbose and repetitive, e.g., 'Generate PDF Document' appears multiple times, and it includes a full endpoint URL and API reference. It could be more concise without losing clarity.

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?

Given the lack of an output schema, the description adequately explains the return value (URL or async handle) and references filtering documentation. It mentions required parameters, making the tool's use clear despite many optional parameters.

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 schema covers all 10 parameters with descriptions (100% coverage), so the baseline is 3. The description only redundantly mentions the required parameter and links to filter documentation, adding minimal new meaning beyond the schema.

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 the tool generates a PDF document from a project and returns a URL. It specifically mentions it applies to Directory records and provides the endpoint, distinguishing it from sibling PDF status check tools.

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?

The description explicitly says 'Use this to perform the generates pdf action on Directory records,' providing clear guidance on when to use it. While it does not list alternatives or exclusions, the sibling tools for checking PDF status implicitly differentiate.

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