Skip to main content
Glama

Preview posting insights

preview_posting_insights
Read-onlyIdempotent

[Read · free] Full breakdown for a previewed profile (from preview_profile): best day, hour, format and length, the top and bottom 5 posts with measured reasons, and engagement trend by format. Requires a free Flux account; calling it asks the person to sign in where the client supports it, otherwise use continue_url from preview_profile.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "preview_id": "<preview_id>"
    },
    "name": "preview_posting_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
preview_idYespreview_id returned by preview_profile

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes well beyond that by disclosing the free/no-credit cost, the account requirement, and the interactive sign-in behavior with a concrete fallback (continue_url) when the client cannot prompt. That auth flow is non-obvious and is exactly the kind of behavior an agent must plan around.

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?

Two sentences, front-loaded with the read/free label and the output summary before the auth caveat. The enumeration of return fields is dense but every clause maps to a distinct deliverable; only the bracketed cost tag is mildly redundant with 'free' later implied by the account requirement.

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 carries the burden of describing results and does so by naming each insight category. It is nearly complete, but leaves open result size and behavior on an expired or claimed preview_id, which an agent would need to handle.

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% and the single parameter preview_id is already documented in the schema, including its provenance. The description restates the same origin (from preview_profile) without adding format, validity window, or reuse semantics, so it neither compensates nor detracts.

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 resource and enumerates exactly what comes back: best day, hour, format and length, top/bottom 5 posts with measured reasons, and engagement trend by format. It distinguishes itself as the preview-profile variant by tying the input to preview_profile, though it never explicitly contrasts itself with the non-preview get_posting_insights sibling, leaving that boundary to inference.

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?

Gives concrete preconditions and a fallback path: it needs a preview_id from preview_profile, requires a free Flux account, prompts sign-in where the client supports it, and otherwise directs the caller to continue_url. What is missing is an explicit statement of when to prefer this over get_posting_insights for an already-claimed profile.

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