Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Company Vendors

list_company_vendors
Read-onlyIdempotent

Retrieve all vendors for a company. Use the minimal view for lightweight dropdown data without extra permissions, or look up a vendor ID before making other Procore API calls.

Instructions

Return a list of all Vendors associated with a Company. Adds support for the minimal view, which returns a reduced payload (id, name, is_active, logo) intended for vendor selector dropdowns. The minimal view does not require the view_vendors Directory permission — it is available to any user authenticated on the Company. All other views continue to require view_vendors. Use this to discover company vendors or to look up the id of one before calling a tool that needs it. Returns a JSON array of company vendors; 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 (v1.1): Core > Directory. Endpoint: GET /rest/v1.1/vendors

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
sortNoQuery string parameter — return items with the specified sort
viewNoQuery string parameter — specifies which view of the resource to return (which attributes should be present in the response). The `minimal` view returns a reduced payload and does not require Directory permissions; all oth...
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
company_idYesQuery string parameter — unique identifier for the company.
filters__id__NoQuery string parameter — returns vendors with the specified id(s)
filters__searchNoQuery string parameter — return vendors where the search string matches the vendor name, keywords, origin_code, or ABN/EIN number
filters__origin_idNoQuery string parameter — origin ID. Returns item(s) with the specified Origin ID.
filters__created_atNoQuery string parameter — return items within a specific created at ISO8601 datetime range
filters__trade_id__NoQuery string parameter — returns vendors associated with the specified trade id(s)
filters__updated_atNoQuery string parameter — return items within a specific updated at ISO8601 datetime range
filters__parent_id__NoQuery string parameter — returns vendors with the specified parent id(s)
filters__standard_cost_code_id__NoQuery string parameter — returns vendors associated with the specified standard cost code id(s)
Behavior5/5

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

Beyond the annotations (readOnlyHint, destructiveHint false), the description explicitly states 'Read-only — it changes nothing in Procore' and adds permission nuances for the minimal view. It also discloses pagination behavior ('reports how many pages remain') and error payload details with common HTTP statuses. This adds substantial context the annotations don't provide.

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?

The description is dense but every sentence contributes: purpose, minimal view explanation, permission contrast, use case, return format, pagination, read-only guarantee, error handling, required parameter, and API endpoint reference. It is front-loaded with the core purpose and doesn't waste words on restating the schema.

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?

For a list tool with no output schema, the description covers return type (JSON array), pagination, permission requirements, error behavior, and required parameter. Combined with full schema coverage and annotations for safety, the agent has enough to select and invoke correctly. No significant gaps remain.

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?

The input schema already documents all 13 parameters with 100% coverage, so baseline is 3. The description adds meaning by explaining the minimal view's reduced payload and purpose, and notes page/per_page control pagination. It also highlights company_id as required, which the schema also lists, but the description integrates this into usage guidance.

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?

The description opens with 'Return a list of all Vendors associated with a Company,' a clear verb+resource statement. It distinguishes this from sibling tools by company scoping and mentions 'discover company vendors or to look up the id of one' before other calls. This unambiguously identifies the operation.

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?

It says 'Use this to discover company vendors or to look up the id of one before calling a tool that needs it,' providing a specific use case. It also notes the minimal view is for dropdowns and doesn't require view_vendors permission, which guides when to use that view. It doesn't explicitly contrast with list_project_vendors, but the company-scoped name and company_id requirement make the scope 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