Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Ecrion Xml And Template For Meetings

list_ecrion_xml_and_template_for_meetings_v1_0
Read-onlyIdempotent

Retrieve Ecrion XML and template data for all meetings on a project. Use to get a paginated overview, find meeting IDs, or filter by parameters. Requires project_id.

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: Project Management > Meetings. Endpoint: GET /rest/v1.0/meetings/ecrion_pdf_generation_data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string 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)
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds that response includes pagination metadata, which is useful but not critical beyond annotations.

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?

Description is concise, front-loaded with purpose, and includes all necessary information without redundancy.

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?

Adequately describes return type (paginated JSON array) and pagination metadata, but lacks details on field structure or error conditions. Still sufficient for a list 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 coverage is 100% with clear descriptions. The tool description does not add new semantic information beyond summarizing usage of page and per_page.

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?

Description explicitly states it returns 'Ecrion Xml and Template for all Meetings on the Project' and specifies using it for paginated overview, finding IDs, or filtering. This clearly distinguishes it from other meeting listing 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?

Provides clear context for when to use (paginated overview, find IDs, filter) and mentions pagination controls, but does not explicitly exclude or mention alternative tools like list_meetings_project.

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