Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Ecrion Xml And Template For Meetings

list_ecrion_xml_and_template_for_meetings_project
Read-onlyIdempotent

Retrieve Ecrion XML and template for all meetings in a project. Filter by various parameters and paginate results.

Instructions

Returns Ecrion Xml and Template for all Meetings on the Project. Use this to enumerate Meetings when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Meetings. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API (v1.1): Project Management > Meetings. Endpoint: GET /rest/v1.1/projects/{project_id}/meetings/ecrion_pdf_generation_data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__assignee_idNoQuery string parameter — returns meeting(s) with the specified assignee
filters__idNoQuery string parameter — returns meeting(s) with the specified ID(s)
filters__publicNoQuery string parameter — returns public meeting(s).
filters__draftNoQuery string parameter — returns draft meeting(s).
filters__modeNoQuery string parameter — returns meeting(s) in certain mode.
filters__root_idNoQuery string parameter — returns child meeting(s) whose root_id matches the specified root_id. Parent is returned as well
filters__rootsNoQuery string parameter — returns Only parent/root meetings
filters__template_idNoQuery string parameter — returns child meeting(s) whose meeting_template_id matches the specified template_id.
show_attachmentsNoQuery string parameter — determine the AttachmentVisible tag value
Behavior4/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds that it returns a paginated JSON array with metadata and requires project_id, which provides additional 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.

Conciseness5/5

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

The description is five sentences, front-loaded with purpose, and each sentence adds value without redundancy. It is efficiently structured.

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 12 parameters, full schema coverage, and annotations, the description provides pagination details, usage context, and API endpoint info. It lacks output schema, but the return format is described as a paginated JSON array. Overall, it is fairly complete.

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 description coverage is 100%, so the schema already documents all parameters. The description adds general guidance on page and per_page for pagination and notes project_id is required, but does not elaborate on filter parameters beyond that.

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 'Returns Ecrion Xml and Template for all Meetings on the Project,' specifying the exact resource and verb. It distinguishes this tool from sibling tools like list_meetings_project by targeting Ecrion XML and template data.

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 says 'Use this to enumerate Meetings when you need a paginated overview, to find IDs, or to filter by query parameters,' providing clear use cases. However, it does not explicitly mention when not to use or suggest 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