Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Meeting Topic

create_meeting_topic_project

Create a new meeting topic in a specified Procore project meeting. Provide project ID, meeting ID, and topic object; optionally upload attachments.

Instructions

Creates 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 create a new Meetings in Procore. Creates a new Meetings and returns the created object on success (HTTP 201). Required parameters: project_id, meeting_id, meeting_topic. Procore API (v1.1): Project Management > Meetings. Endpoint: POST /rest/v1.1/projects/{project_id}/meeting_topics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
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?

Adds information about multipart/form-data for attachments and HTTP 201 success response, but lacks details on side effects, auth requirements, or idempotency 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat repetitive (e.g., repeats 'Creates a new Meetings' twice) and could be more concise. The attachment upload section is detailed but verbose.

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?

Missing explanation of the meeting_topic object's structure (it has additionalProperties, which is very generic). No output schema, so the return value is unclear. The description is incomplete for an agent to effectively use the tool.

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 3. The description adds multipart details for attachments but not for other parameters like project_id or meeting_topic object structure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it creates a meeting topic, but it incorrectly says 'Creates a new Meetings' which is ambiguous. It does not distinguish from sibling tools like create_meeting_v1_0 or create_meeting_topic_v1_0.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. It says 'Use this to create a new Meetings in Procore' but does not compare with other meeting-related tools.

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