Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Counts Of Daily Logs

list_counts_of_daily_logs_project
Read-onlyIdempotent

Returns paginated counts of daily logs by type, filtered by date, status, or creator, based on user permissions. Use to enumerate log records and find IDs.

Instructions

Returns counts of all daily logs arranged by type, given the current user permissions. Read Only/Standard users will see only counts of approved logs, Collaborator users will see only counts of logs created by themselves, Admins can use filter options to see all logs, or only a specific approval status (defaulting to approved). See Working with Daily Logs for information on filtering the response using the log_date, start_date, and... Use this to enumerate Daily Log records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Daily Log records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Daily Log. Endpoint: GET /rest/v1.0/projects/{project_id}/daily_logs/count

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
log_dateNoQuery string parameter — date of specific logs desired in YYYY-MM-DD format
start_dateNoQuery string parameter — start date of specific logs desired in YYYY-MM-DD format (use together with end_date)
end_dateNoQuery string parameter — end date of specific logs desired in YYYY-MM-DD format (use together with start_date)
filters__statusNoQuery string parameter — filter on status for "pending" or "approved" or "all"
filters__created_by_idNoQuery string parameter — returns item(s) created by the specified User IDs.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior3/5

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

Adds value beyond annotations by describing permission-based filtering behavior and pagination metadata. However, there is an internal contradiction: returning counts vs. a paginated array of records, which reduces clarity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and includes repeated information about pagination. It is front-loaded with purpose but could be more concise and better structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks a clear description of the output format (counts vs. records) and does not resolve the internal contradiction. Without an output schema, the description should explicitly state the response structure.

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 has 100% coverage, so description adds limited value. It mentions the endpoint and pagination control, but does not deepen parameter understanding beyond 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 counts of daily logs arranged by type, but also mentions enumerating Daily Log records (which is contradictory) and does not differentiate from the sibling list_counts_of_daily_logs_project_v1_1.

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?

Provides role-based usage context (Read Only, Collaborator, Admin) and mentions filtering, but no explicit when-not-to-use or alternatives among many sibling tools. The phrase 'Use this to enumerate Daily Log records' is misleading.

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