Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

List Filters

list_filters_company
Read-onlyIdempotent

Retrieve a paginated list of available filters for a company to enumerate project-level configuration records and find filter IDs.

Instructions

Return a list of available filters. Use this to enumerate Project-Level Configuration records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Project-Level Configuration records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API: Company Admin > Project-Level Configuration. Endpoint: GET /rest/v1.0/companies/{company_id}/filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent. Description adds pagination behavior and return format (JSON array with metadata). 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.

Conciseness5/5

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

Three sentences covering purpose, usage, and technical details (endpoint, required params). Each sentence serves a clear function, no redundancy.

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 simple list endpoint: purpose, usage, pagination, required parameter, API reference. No output schema needed as return type is implied.

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 covers all three parameters with detailed descriptions (company_id, page, per_page). Description only reiterates pagination usage, adding minimal new value 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?

Description clearly states it returns a list of available filters for Project-Level Configuration records, distinguishing from project-level filter lists. The verb 'return a list' and resource 'available filters' are specific.

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?

Describes use cases: enumerating records, paginated overview, finding IDs, filtering. However, does not mention when not to use or alternative tools like list_filters_project.

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