Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Meeting

update_meeting_project

Update an existing meeting in a Procore project by providing only the fields to change. Supports file attachments via multipart/form-data.

Instructions

Update a Meeting. #### 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: project_id, id, project_id, meeting. Procore API (v1.1): Project Management > Meetings. Endpoint: PATCH /rest/v1.1/projects/{project_id}/meetings/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesJSON request body field — the ID of the Project the Meetings belongs to
idYesURL path parameter — unique identifier of the Meetings resource
meetingYesJSON request body field — meeting object
attachmentsNoJSON request body field — meeting 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.
Behavior4/5

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

Describes partial update behavior and multipart/form-data requirement for attachments. Annotations already indicate non-read-only, non-destructive, non-idempotent, so description adds useful context beyond structured fields.

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?

Description is verbose with repetition (e.g., 'Uploading attachments' block appears twice). Includes extraneous API reference line. Could be more concise and better front-loaded.

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?

Covers update semantics and attachment specifics but lacks explanation of meeting object fields or return structure. With no output schema, description should provide more detail on what is returned.

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%, so baseline is 3. Description repeats required parameters and adds attachment upload detail already in schema. Does not elaborate on the 'meeting' object structure beyond what schema provides.

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?

Clearly states 'Update a Meeting' and specifies it updates an existing meeting, returning the modified object. Differentiated from siblings like create and list tools through the action verb and resource.

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?

Explicitly says 'Use this to update an existing Meetings' and notes that only supplied fields are changed. Provides required parameters but lacks explicit alternatives or when-not-to-use conditions.

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