Skip to main content
Glama
Sign In
reelfaceless-mcp

reelfaceless-mcp

by danyial
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_post_metrics

Retrieve latest platform metrics for a published post, including views, likes, and comments per channel. Data reflects the last analytics sync.

Instructions

Get the latest platform metrics (views, likes, comments) per channel for a published post, as of the last analytics sync.

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": {
      "post_id": "<post_id>"
    },
    "name": "get_post_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well by noting the metrics are 'as of the last analytics sync', indicating potential staleness. It implies a read-only operation, but could further clarify permissions or rate limits.

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?

The description is a single, direct sentence that conveys the tool's purpose and key behavioral nuance (analytics sync latency) without wasted words.

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?

For a simple one-parameter read tool without output schema, the description covers the main behavior and data freshness. It does not detail the output structure, but that is partially mitigated by the simplicity of metrics.

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

Parameters1/5

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

The sole parameter post_id has 0% schema description coverage, and the description adds no extra guidance beyond its type (uuid). The agent receives no hints on how to obtain the value (e.g., from list_posts) or any constraints.

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?

The description clearly states the tool retrieves 'latest platform metrics (views, likes, comments) per channel for a published post, as of the last analytics sync'. This distinguishes it from sibling tools like get_post_status (status only) and list_channels (channel listing).

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

Usage Guidelines2/5

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

The description lacks explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., post must be published) or scenarios where other tools like get_post_status or list_posts would be more appropriate.

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