Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project Vendors

list_project_vendors
Read-onlyIdempotent

Retrieve a paginated list of vendors for a specified project. Filter by name, trade, cost code, or ID to find specific records.

Instructions

Return a list of Vendors associated with a specified Project. 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: project_id. Procore API (v1.1): Core > Directory. Endpoint: GET /rest/v1.1/projects/{project_id}/vendors

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
viewNoQuery string parameter — specifies which view of the resource to return (which attributes should be present in the response). Users without read permissions to Directory are limited to ids_only, name, and minimal views. If...
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__searchNoQuery string parameter — return vendors where the search string matches the vendor name, keywords, origin_code, or ABN/EIN number
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 declare readOnlyHint=true and destructiveHint=false. The description adds behavioral details beyond annotations: pagination (page, per_page control), response as 'paginated JSON array with pagination metadata', and the specific API endpoint. This provides useful context not found in annotations.

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 four sentences, front-loaded with purpose, then usage, then response details, then API provenance. No unnecessary words; every sentence adds value.

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?

For a list tool with 10 parameters and no output schema, the description covers pagination, required parameter, response format, and API info. It could mention that the response contains vendor details, but the schema covers parameters. Annotations cover safety. Overall adequate.

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 does not need to duplicate parameter docs. It adds limited value by mentioning pagination control and required project_id, but does not elaborate on filter parameters or view options beyond schema. Baseline 3 is appropriate.

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 tool returns 'a list of Vendors associated with a specified Project', specifying a specific verb and resource. It adds usage context (enumerate, find IDs, filter) and the resource is distinct from sibling list tools like list_company_vendors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides usage scenarios (enumerate, find IDs, filter) but does not explicitly exclude alternatives or mention when not to use this tool compared to sibling tools. The guidance is implicit rather than explicit.

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