Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Workflow Activity History

create_workflow_activity_history

Records a workflow activity to transition the workflow instance to the next state by providing required IDs and optional comments.

Instructions

Perform a workflow activity. Workflows Instances transition between states when all required activities have been performed. Use this to create a new Workflows in Procore. Creates a new Workflows and returns the created object on success (HTTP 201). Required parameters: workflow_instance_id, company_id, workflow_activity_id, workflow_instance_id, workflow_user_role_id, performed_by_id. Procore API: Core > Workflows. Endpoint: POST /rest/v1.0/workflow_activity_histories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_instance_idYesJSON request body field — workflow Instance ID
company_idYesQuery string parameter — unique identifier for the company.
workflow_activity_idYesJSON request body field — workflow Activity ID
workflow_user_role_idYesJSON request body field — workflow User Role ID
performed_by_idYesJSON request body field — login Information ID of a Workflow User Role Login Information.
commentsNoJSON request body field — the comments for this Workflows operation
attachmentsNoJSON request body field — 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.
Behavior2/5

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

Annotations indicate non-readOnly and non-destructive behavior. The description adds that it returns HTTP 201 on success, but fails to disclose that performing a workflow activity may trigger state transitions, requires certain permissions, or has side effects. It also inaccurately states 'Creates a new Workflows', which is misleading.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description contains redundancy ('Creates a new Workflows' repeated) and lists parameters in a run-on sentence. It lacks clear structure and could be significantly more concise.

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?

With 7 parameters and no output schema, the description does not explain the return structure, error handling, or the concept of workflow activity history. It misses essential context about state transitions and prerequisites, making it incomplete for an agent.

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 parameter descriptions. The description lists required parameters but adds minimal extra meaning; it mentions the endpoint but does not explain parameter relationships or usage nuances. Baseline 3 applies due to high schema coverage.

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 states 'Perform a workflow activity' and 'Creates a new Workflows in Procore', which indicates the tool creates a workflow activity history entry. However, it inaccurately says 'create a new Workflows', causing confusion. Overall, the verb and resource are identifiable, distinguishing it from list and show siblings.

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?

The description lists required parameters but provides no guidance on when to use this tool versus alternatives, such as when to create a workflow instance versus recording activity history. There is no mention of prerequisites or cases where this tool should not be used.

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