Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Meeting Attendee Record

update_meeting_attendee_record
Idempotent

Update an existing meeting attendee record in Procore. Specify only the fields to change; unchanged fields remain. Requires meeting, project, and record IDs.

Instructions

Updates an existing meeting attendee record in Procore. Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "meeting_attendee_record" in the request payload for you. id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified meeting attendee record on success. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: meeting_id, project_id, id. Procore API: Project Management > Meetings. Endpoint: PATCH /rest/v1.0/meeting_attendee_records/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — iD of the Meeting Attendee record
statusNoJSON request body field — attendance status
meeting_idYesQuery string parameter — unique identifier of the meeting
project_idYesQuery string parameter — unique identifier for the project.
login_information_idNoJSON request body field — the ID of the User to associate with the Meeting
Behavior5/5

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

Goes well beyond annotations by detailing partial-update semantics (omitted fields keep values), payload nesting (top-level args mapped to 'meeting_attendee_record'), and failure behavior (HTTP statuses 401/403/404). This is rich, actionable transparency that the annotations alone do not provide.

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 long but every sentence carries value: purpose, partial update, parameter passing, id resolution, return value, errors, and API reference. It is logically ordered and front-loaded, though slightly verbose.

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

Completeness5/5

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

For a tool with 5 parameters, no output schema, and moderate complexity, the description covers all necessary aspects: purpose, usage, parameter handling, return value, failure modes, and endpoint. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions cover all parameters, but the description adds crucial invocation semantics: fields are passed as top-level arguments despite being nested in the payload, and id must be resolved via a list tool. This is meaningful context beyond the schema.

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 opens with 'Updates an existing meeting attendee record in Procore', a precise verb+resource statement. It distinguishes from create/delete siblings by using 'existing' and providing the PATCH endpoint, leaving no ambiguity about the tool's role.

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?

It gives explicit how-to guidance: send only changed fields, resolve id via the matching list tool, and the required parameters are listed. It does not explicitly name alternative tools or state when not to use it, but the context is clear enough for an agent to decide.

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