Skip to main content
Glama
TylerIlunga

Procore MCP Server

List App Configurations

list_app_configurations
Read-onlyIdempotent

Retrieve app configurations for a company or project to discover available configurations and find their IDs before using other tools. Read-only, supports pagination and filtering.

Instructions

Returns a list of app configurations on a given company or project. Use this to discover app configurations or to look up the id of one before calling a tool that needs it. company_id defaults to the value set by procore_set_config when omitted. Returns a JSON array of app configurations; page and per_page control pagination and the response reports how many pages remain. Read-only — it changes nothing in Procore. 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: company_id. Procore API: Platform - Developer Tools > App Marketplace. Endpoint: GET /rest/v1.0/companies/{company_id}/app_configurations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
sortNoQuery string parameter — direction (asc/desc) can be controlled by the presence or absence of '-' before the sort parameter.
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
company_idYesURL path parameter — unique identifier for the company.
filters__project_idNoQuery string parameter — filter results by project id
filters__app_installation_idNoQuery string parameter — filter results by app installation id
Behavior5/5

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

Goes beyond annotations by describing return format as a JSON array, pagination behavior ('page and per_page control pagination and the response reports how many pages remain'), read-only nature explicitly, and failure modes with HTTP status meanings (401/403/404).

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?

Purpose is front-loaded and every sentence adds information. The API reference and error-status details add length but provide useful context; still reasonably concise for the amount of behavior covered.

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?

Covers return type, pagination, defaults, error handling, and required parameters. Without an output schema, it doesn't detail the array's item fields, but the mention of looking up IDs implies the structure. Adequate for a list tool.

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%, so baseline is 3. The description adds value by explaining the company_id default from procore_set_config and the role of page/per_page in pagination, which is extra context beyond the schema descriptions.

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?

Clear verb+resource: 'Returns a list of app configurations on a given company or project.' It also states a specific use case for discovering configurations and looking up IDs, which distinguishes it from show/create tools.

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 a clear context: 'Use this to discover app configurations or to look up the id of one before calling a tool that needs it.' Also notes default company_id behavior and pagination. No explicit alternatives or when-not-to-use, so a 4 rather than 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