Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Workflow Permanent Logs

list_workflow_permanent_logs_company
Read-onlyIdempotent

Retrieve a paginated list of workflow permanent logs filtered by workflowed object type and ID for a company.

Instructions

Return a list of workflow permanent logs. Any resource using workflow should have log of activities and events related to the workflow. See Filtering on List Actions for information on using the filtering capabilities provided by this endpoint. Use this to enumerate Workflows when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, filters[workflowed_object_type], filters[workflowed_object_id]. Procore API: Core > Workflows. Endpoint: GET /rest/v1.0/companies/{company_id}/workflow_permanent_logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__workflowed_object_typeYesQuery string parameter — filter log(s) with matching workflowed object type
filters__workflowed_object_idYesQuery string parameter — filter log(s) with matching workflowed object id
Behavior4/5

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

Annotations already declare read-only, non-destructive, idempotent. Description adds pagination details, required params, and links to filtering docs. No contradictions.

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?

Informative paragraph with no wasted sentences, but slightly verbose with external link and API details; still efficient.

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?

Complete for a list tool: purpose, usage, pagination, filtering, required params, and output type. Handles all necessary context given annotations and schema.

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 has 100% description coverage; description reinforces required params and pagination, but adds no new meaning 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 it lists workflow permanent logs, with specific resource 'workflow permanent logs' and verb 'list'. Differentiates from sibling 'list_workflow_permanent_logs_project' by company scope.

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?

Provides context for using the tool: to enumerate workflows, find IDs, filter by query params. Mentions pagination and required params. Lacks explicit 'when not to use' or direct sibling comparison.

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