Skip to main content
Glama
meertrack

Meertrack MCP

Official
by meertrack

Get activity items

get_activity_items
Read-only

Retrieve full activity details for 1–100 rows in a single API call. Returns section-specific content omitted by list_activities, with not_found for unresolved IDs.

Instructions

Wraps GET /activity/items. Returns the full payload for one or more activity rows — the section-specific detail (full blog description, key points, pricing table, etc.) that the list_activities feed omits to stay lean.

Pass a list of row ids from a list_activities result (1–100). Resolving several at once is one call / one rate-limit hit — prefer it over many single lookups. Partial success is normal: ids that don't resolve (unknown, in another workspace, from an inactive period, or malformed) come back in not_found, not as an error. data order is not guaranteed — match results back by id. Digest ids are NOT activity rows: they land in not_found. Use get_digest for those. Errors: unauthorized, rate_limited, invalid_parameter (no ids / too many).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
row_uuidsYes1–100 activity row ids to resolve in one batch.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
not_foundYes
Behavior5/5

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

Annotations only say readOnlyHint=true; description adds critical behavioral traits: partial success with not_found, data order not guaranteed, digest ids invalid, and error types. Adds significant value.

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?

Well-structured with clear sections: purpose, usage guidelines, caveats, errors. Every sentence earns its place, no redundancy.

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?

With output schema present, description need not detail return values, but covers not_found and ordering. Includes error types and edge cases. Complete for tool complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers row_uuids well (format, constraints). Description adds context: source from list_activities, prefers batch, and ids from digest not valid. Adds value beyond schema.

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?

Clearly states it wraps GET /activity/items to return full payload for activity rows, and distinguishes from list_activities which is lean. Also mentions batch resolution and partial success.

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

Usage Guidelines5/5

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

Explicitly says to use after list_activities, prefers batch over many single lookups due to rate limits, and advises that digest ids should go to get_digest. Also lists errors.

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/meertrack/meertrack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server