Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Workflow Presets (Company)

list_workflow_presets_company
Read-onlyIdempotent

Enumerate workflow presets for a company using pagination and filters. Specify company ID and tool type to retrieve preset IDs and configuration details.

Instructions

List Workflow Presets (Company). 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[tool_type]. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/workflows/presets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__tool_typeYesQuery string parameter — filter results by tool type
filters__tool_subtypeNoQuery string parameter — filter by tool subtype
filters__is_defaultNoQuery string parameter — filter by default preset. When true, returns only presets marked as default. When false, returns only non-default presets.
filters__is_validNoQuery string parameter — filter by configuration validity. When true, returns only presets with valid configuration (no configuration or external errors). When false, returns only presets with invalid configuration. When o...
pageNoPage number for paginated results (default: 1)
Behavior4/5

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

Adds context beyond annotations: pagination details, required parameters, endpoint info. Aligns with readOnlyHint=true, destructiveHint=false, idempotentHint=true.

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

Conciseness5/5

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

Four sentences, front-loaded with purpose, each sentence informative. No redundant content.

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

Completeness4/5

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

Given full schema coverage and annotations, description is adequate for a list tool. Covers pagination, required params, and endpoint. Lacks details on response metadata but not critical.

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 is 3. Description adds value by summarizing required params and pagination use, but doesn't add significant new meaning beyond 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?

Directly states 'List Workflow Presets (Company)' and elaborates on use cases: paginated overview, ID retrieval, filtering. Clearly distinguishes from siblings like list_workflow_presets_project.

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?

States when to use: for paginated overview, IDs, filtering. Implicitly distinguishes from sibling tools by specifying company scope, but lacks explicit alternatives or when not to use.

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