Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Company Vendors

list_company_vendors
Read-onlyIdempotent

Retrieve a paginated list of all vendors associated with a company. Use to find vendor IDs or filter by search, trade, or cost codes.

Instructions

Return a list of all Vendors associated with a Company. Use this to enumerate Directory records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Directory records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API: Core > Directory. Endpoint: GET /rest/v1.0/vendors

Input Schema

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

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

Annotations already indicate read-only and non-destructive behavior. The description adds value by explaining the return format ('paginated JSON array of Directory records') and pagination metadata, which goes beyond the annotations.

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?

The description is concise with key information front-loaded. It includes API details (Procore API, endpoint) without excessive length, though it could be slightly more streamlined.

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 the rich schema and annotations, the description covers the essential aspects: purpose, pagination, required parameter, and returns. It lacks details on output schema, but that is not required as no output schema is provided.

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 the description contributes limited additional meaning. It mentions pagination parameters (page, per_page) and required company_id, but does not elaborate beyond what the schema provides, meeting the baseline.

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 clearly states the verb 'Return' and the resource 'list of all Vendors associated with a Company.' It specifies that it is used for paginated overviews, finding IDs, and filtering, distinguishing it from generic 'list' siblings.

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?

The description provides clear usage scenarios (enumerate directory records, paginated overview, find IDs, filter by query parameters). It does not explicitly state when not to use or offer alternatives, but the context is sufficient.

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