Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Timecard Entries (Company)

list_timecard_entries_company
Read-onlyIdempotent

Retrieve paginated timecard entries by company ID, with filters for IDs, dates, and status. Enables enumeration of field productivity records for analysis or integration.

Instructions

Return a list of all Timecard Entries, serialized according to the MyTime field set. Use this to enumerate Field Productivity records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Field Productivity records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API: Project Management > Field Productivity. Endpoint: GET /rest/v1.0/companies/{company_id}/timecard_entries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__party_idNoQuery string parameter — return item(s) with the specified Party ID.
filters__in_progress_onlyNoQuery string parameter — return work in progress item(s).
filters__include_in_progressNoQuery string parameter — return available and work in progress item(s).
filters__updated_atNoQuery string parameter — return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYY...
filters__deleted_atNoQuery string parameter — return item(s) that were deleted within the specified ISO 8601 datetime range.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
start_dateNoQuery string parameter — the beginning of the date range for entries. (YYYY-MM-DD)
end_dateNoQuery string parameter — the ending of the date range for entries. (YYYY-MM-DD)
start_time_inNoQuery string parameter — the beginning of the time_in range for entries (YYYY-MM-DDTHH:MM:SSZ). "Z" represents the timezone offset (i.e. -08:00, -0800). Optionally you may pass the literal "Z" which also means "UTC".
end_time_inNoQuery string parameter — the ending of the time_in range for entries (YYYY-MM-DDTHH:MM:SSZ). "Z" represents the timezone offset (i.e. -08:00, -0800). Optionally you may pass the literal "Z" which also means "UTC".
use_filter_tzNoQuery string parameter — when passed as "true" the timezone from start_time_in or end_time_in will be used for all timestamps in the response. Otherwise they'll use UTC.
serializer_viewNoQuery string parameter — changes what fields are included in the response.
Behavior4/5

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

Annotations already indicate read-only and idempotent. The description adds that the response is a paginated JSON array with pagination metadata, and mentions serialization according to MyTime field set, which provides extra context 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 four sentences, front-loading the purpose and usage guidance. It includes the API endpoint, which is extraneous but not excessive. Efficient with no wasted words.

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 15 parameters with full schema descriptions, no output schema, and annotations indicating open world, the description provides a high-level overview and pagination details. Minor gap: 'serialized according to the MyTime field set' is unclear, but overall sufficient.

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 baseline is 3. The description adds minimal parameter context (page and per_page for pagination), but does not explain other filter parameters beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns a list of timecard entries with pagination and filtering. It specifies the resource (timecard entries) and action (list), but does not explicitly distinguish from sibling tools like list_timecard_entries_project or list_timecard_entries.

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 suggests using this tool for paginated overviews, finding IDs, or filtering, but lacks explicit guidance on when not to use it or alternatives (e.g., for single entry use show_timecard_entry_company, for project-level use list_timecard_entries_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