Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda List Page Analytics

coda_list_page_analytics
Read-onlyIdempotent

Retrieve per-page usage metrics, such as views and unique views, for a Coda doc to identify which pages receive the most traffic. Available to doc owners.

Instructions

List analytics data for pages within a doc.

Returns per-page usage metrics (views, unique views) for the specified doc. Only available to doc owners. Useful for understanding which pages get the most traffic.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (1-200)
cursorNoPagination cursor from a previous response
doc_idYesThe doc ID to get page analytics for
since_dateNoStart date for analytics (ISO 8601)
until_dateNoEnd date for analytics (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.4.14

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: an authorization constraint (doc owners only) and the shape of the returned metrics (views, unique views). It omits pagination behavior despite the cursor parameter.

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?

Three short sentences, front-loaded with the action and immediately followed by the return contents. The closing sentence about traffic is mildly promotional but does carry usage intent, so no major waste.

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?

With no output schema, the description does partially carry the return-value burden by naming views and unique views, and it covers the access requirement. Missing pagination/date-range semantics and result ordering, which an agent would need for full confidence.

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 description coverage is 100%, so every parameter including limit, cursor, since_date and until_date is already documented in the schema. The description adds only that doc_id identifies the target doc, which the schema already states — baseline 3 applies.

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?

States a specific verb+resource ('List analytics data for pages within a doc') and specifies the unit of analysis — per-page metrics — which separates it from the doc-level siblings coda_list_doc_analytics and coda_get_doc_analytics_summary. It stops short of naming those siblings explicitly, so the routing distinction is implied rather than stated.

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?

Gives a prerequisite ('Only available to doc owners') and a motivating use case ('understanding which pages get the most traffic'), but never says when to prefer this over the other analytics tools in the sibling set, nor what to do when owner access is unavailable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools