Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Workflow Activity History

create_workflow_activity_history

Log a workflow activity to transition a workflow instance, creating a history record that tracks performed actions.

Instructions

Perform a workflow activity. Workflows Instances transition between states when all required activities have been performed. Pass the record's fields as top-level arguments — they are nested under "workflow_activity_history" in the request payload for you. Creates the workflow activity history and returns it with its new id (HTTP 201); calling it again creates another record. 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: workflow_instance_id, company_id, workflow_activity_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
commentsNoJSON request body field — the comments for this Workflows operation
company_idYesQuery string parameter — unique identifier for the company.
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.
performed_by_idYesJSON request body field — login Information ID of a Workflow User Role Login Information.
workflow_activity_idYesJSON request body field — workflow Activity ID
workflow_instance_idYesQuery string parameter — workflow Instance ID
workflow_user_role_idYesJSON request body field — workflow User Role ID
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses key behaviors: calling again creates another record (non-idempotent), returns HTTP 201 with new id, and error payloads with 401/403/404 statuses. It also explains payload nesting. This significantly exceeds the structured data.

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 moderately long but information-dense. It front-loads the main action and includes practical details (errors, endpoint). A few clauses could be tightened, but each sentence provides useful information without excessive fluff.

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?

Given no output schema, the description covers return behavior (new id, HTTP 201), failure modes, required parameters, and API context. It is complete for an agent to invoke the tool and interpret the result. The endpoint reference adds further completeness.

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 coverage is 100% with descriptive parameter entries, so the baseline is 3. The description adds valuable context by explaining that top-level arguments are nested under 'workflow_activity_history' in the payload, which helps the agent correctly map parameters. It also lists required parameters, though redundant with 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 clearly states the action: 'Perform a workflow activity' and 'Creates the workflow activity history'. It distinguishes the tool from sibling list/show tools by emphasizing the create/performs action and provides the endpoint. The verb+resource is specific and unambiguous.

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 provides clear context: workflow instances transition when activities are performed, implying this tool advances the workflow. However, it does not explicitly name alternatives like list_workflow_activity_histories or show_workflow_activity_history or state when not to use them. No exclusions are given, so it falls short of a 5.

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