Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

List Assignees For Accessible Tasks

list_assignees_for_accessible_tasks
Read-onlyIdempotent

Retrieve users assigned to task items you can access in a project. Paginate results to find assignee IDs or filter by query parameters.

Instructions

Returns Users assigned to task items that the current user has access to. Use this to enumerate Tasks when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Tasks. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Core > Tasks. Endpoint: GET /rest/v1.0/task_items/assignees/current

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number 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 declare readOnlyHint=true and destructiveHint=false. Description adds value by specifying paginated JSON array with metadata, and mentions required parameter project_id and pagination parameters.

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?

Several concise sentences, front-loaded with purpose. No unnecessary words. Efficiently conveys key information.

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?

Given no output schema, description adequately explains return type ('paginated JSON array of Tasks' with metadata) and provides endpoint info. Fully informs agent of what to expect.

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% with descriptions for all parameters. Description only reiterates that page/per_page control pagination and project_id is required, adding minimal extra meaning.

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?

Describes specific verb 'Returns' and resource 'Users assigned to task items'. Clearly states purpose and differentiates from siblings by specifying scope (accessible to current user).

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 clear contexts: 'enumerate Tasks when you need a paginated overview, to find IDs, or to filter by query parameters'. Mentions pagination control but does not explicitly state when not to use or list alternatives.

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