Skip to main content
Glama

Eurekuh

Everything the accounts posted

list_network_posts
Read-onlyIdempotent

Every post the organization's connected accounts made on their networks, through Eurekuh or by hand in the network's own app, newest first: platform, accountId, postedAt, url, mediaType and viaEurekuh. Eurekuh reads the networks every few hours, so the newest posts can be missing for a while. Ids, times and links only: get_instagram_stats and get_video_stats have the numbers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_network_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many, 1 to 200. Default 100.
sinceNoOnly posts from this ISO 8601 time on.
accountIdNoOnly this account (an id from list_accounts).
organizationIdNoWhich organization to act in: an id from list_organizations. Leave out for this connection's default organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent and open-world, and the description adds genuinely new behavior: ingestion lag ('Eurekuh reads the networks every few hours, so the newest posts can be missing'), return ordering, and the fact that posts made directly in the native app are included. The staleness caveat is exactly the kind of context an agent needs to avoid drawing wrong conclusions from a short result.

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?

Two dense sentences, front-loaded with the resource definition and its scope, followed by the freshness caveat and the sibling routing. No redundant restatement of the title or of annotation-declared traits.

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 compensates by listing the returned fields and the sort order, and it flags ingestion lag. Remaining gaps are modest: no statement about how to retrieve results beyond the limit (no cursor/paging hint) and no explicit disambiguation from list_posts.

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 limit, since, accountId and organizationId are already well documented, and the default-organization behavior is spelled out in the schema. The description adds only indirect hints (account scoping, recency ordering) and no format or default detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Every post the organization's connected accounts made'), then enumerates the returned fields (platform, accountId, postedAt, url, mediaType, viaEurekuh) and the ordering ('newest first'). The closing clause naming get_instagram_stats/get_video_stats as the numbers-oriented siblings makes it distinguishable from the stats tools.

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?

Explicitly routes numeric/reporting needs to get_instagram_stats and get_video_stats ('Ids, times and links only'), which is a real when-to-use-else signal. It does not, however, contrast itself with the sibling list_posts, which an agent could plausibly confuse with this tool given the near-identical name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources