Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Meetings

list_meetings_project
Read-onlyIdempotent

Retrieve a paginated list of meetings for a project. Filter by assignee, ID, or deleted status to find specific meetings.

Instructions

Returns a list of all Meetings for a specified 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

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)
deleted_onlyNoQuery string parameter — indicates whether to only show deleted meetings. When this query parameter is passed the response body will be an array of meetings without grouping. i.e. { "meetings":[{Meeting_1}, {Meeting_2}] }
filters__assignee_idNoQuery string parameter — returns meeting(s) with the specified assignee
filters__idNoQuery string parameter — returns meeting(s) with the specified ID(s)
serializer_viewNoQuery string parameter — the data set that should be returned from the serializer. The normal view includes default fields. The extended view includes the default fields plus Meeting Template fields. Default view is normal.
Behavior4/5

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

Annotations already set readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds context beyond this by explaining that the response is paginated and includes metadata, and that pagination is controlled via page and per_page parameters.

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?

The description is concise, using a few sentences to convey the purpose, usage, pagination, and required parameters. The inclusion of the API endpoint and version is helpful but slightly redundant for the tool's core function.

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?

The description covers the key aspects: it returns a paginated list of Meetings, requires project_id, and supports pagination. However, it does not detail the structure of each Meeting object, which would be helpful given the lack of an output schema.

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 input schema has 100% parameter descriptions, so the baseline is 3. The description adds value by summarizing pagination usage and noting the required project_id, but does not provide new semantics beyond what the schema already conveys.

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 verb ('Returns a list') and the resource ('all Meetings for a specified Project'). It distinguishes from siblings by specifying the required project_id and endpoint path, which is unique among the many meeting-related 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 tells when to use the tool: to enumerate Meetings for paginated overview, find IDs, or filter by query parameters. It does not, however, list when not to use it or provide direct comparisons to alternative tools like list_meetings_v1_0.

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