Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Meeting Topic

update_meeting_topic_v1_0

Update an existing meeting topic in Procore by specifying its project, meeting, and topic fields, with optional file attachments.

Instructions

Update an existing Meeting Topic. #### Uploading attachments To upload attachments you must upload the entire payload as multipart/form-data content-type and specify each parameter as form-data together with attachments[] as files. Use this to update an existing Meetings (only the supplied fields are changed). Updates the specified Meetings and returns the modified object on success. Required parameters: id, project_id, meeting_id, meeting_topic. Procore API: Project Management > Meetings. Endpoint: PATCH /rest/v1.0/meeting_topics/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — iD of the meeting topic
project_idYesJSON request body field — the ID of the Project the Meeting Topic belongs to
meeting_idYesJSON request body field — the ID of the Meeting the Meeting Topic belongs to
meeting_topicYesJSON request body field — meeting topic object
attachmentsNoJSON request body field — an array of the Attachments of the Meeting Topic. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together wit...
Behavior3/5

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

Annotations already indicate non-read-only and non-destructive behavior. The description adds context about multipart/form-data for attachments but does not disclose idempotency or other side effects. OpenWorldHint is true but not explained.

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 is somewhat verbose with redundancy (e.g., 'Update an existing Meeting Topic' and later 'Use this to update an existing Meetings'). It could be more concise by removing repeated information and focusing on essential usage details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks explanation of the return value (modified object) and does not describe error cases or prerequisites. The nested 'meeting_topic' parameter is not detailed, leaving the agent without enough context for correct invocation.

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 descriptions for all parameters. The description lists required parameters but does not add significant meaning beyond the schema, such as explaining the nested 'meeting_topic' object structure.

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 verb 'Update' and the resource 'existing Meeting Topic', and it provides the endpoint. It is specific enough but does not explicitly differentiate from sibling update tools like 'update_meeting_topic_project'.

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?

The description states when to use it ('Use this to update an existing Meetings') and lists required parameters, but it does not provide when-not-to-use guidance or compare with alternatives like the create tool.

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