Skip to main content
Glama
Sign In

PopOff Data

by tv.popoff
OverviewDiscussionsAdmin

Get engagement rates

get_engagement
Read-only

Engagement rates for a contestant's profiles: current, baseline, and 30-day history (likes/comments-based).

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": {
      "contestant": "<contestant>"
    },
    "name": "get_engagement"
  }
}

Input Schema

NameRequiredDescriptionDefault
contestantYesContestant ID or slug, e.g. "394" or "amora-cachee".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The description complements the readOnlyHint annotation by explaining what kind of data is returned: current, baseline, and 30-day history based on likes and comments. It does not describe internal side effects or edge cases, but the annotation already covers the read-only safety profile.

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 one concise sentence that leads with the result type, then defines the scopes and metric basis. Every phrase is informative and there is no redundant filler.

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 single-parameter read-only tool with no output schema, the description adequately conveys the output dimensions: current, baseline, and 30-day history. It is not overly explicit about response formatting, but the tool is simple enough that this is unlikely to hinder correct invocation.

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?

The only parameter, contestant, is already documented in the schema with ID or slug examples and 100% coverage. The description adds little beyond restating that the engagement rates belong to a contestant's profiles, so it does not improve on the schema.

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?

The description clearly specifies what is returned: engagement rates for a contestant's profiles, including current, baseline, and 30-day history. It distinguishes from sibling tools by focusing on engagement rates rather than follower counts or events, but it does not explicitly contrast itself with those siblings.

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?

The description gives clear context for when to use this tool: when you need engagement rates for a contestant's profile. It does not explicitly state when not to use it or name alternative tools, but the scope is clear enough for a simple 1-parameter read-only lookup.

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

All PopOff Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources