Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Possible Tool Filter Values

list_possible_tool_filter_values
Read-onlyIdempotent

Retrieve all possible filter values for a specified filter in Procore projects. Use to find available filter options for commitments, change orders, or direct costs.

Instructions

List all possible values customer can apply to a filter. Use this to enumerate Portfolio records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Portfolio records. Required parameters: id, filter_name, tool, tab. Procore API: Core > Portfolio. Endpoint: GET /rest/v1.0/projects/{id}/filters/{filter_name}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier for the project.
filter_nameYesURL path parameter — the filter name for this Portfolio operation
toolYesQuery string parameter — tool name
tabYesQuery string parameter — tab name
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds return type (JSON array), pagination context (via page/per_page params), and scope (Portfolio records). 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?

Four sentences: action, use cases, return format, required params and API details. Efficient but repeats required parameter info already in schema.

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?

Specifies return type (JSON array) and endpoint. Does not detail pagination behavior or error handling, but annotations cover safety. Adequate for a list tool.

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% coverage; description mentions required parameters but adds no new meaning beyond schema. Baseline score for high coverage.

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 all possible filter values for Portfolio records, with specific use cases (paginated overview, finding IDs, filtering). Differentiates from sibling list_* tools by focusing on filter values.

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 explicit use cases ('enumerate Portfolio records when you need a paginated overview, to find IDs, or to filter by query parameters') and lists required parameters. Lacks 'when not to use' but context is clear.

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