Skip to main content
Glama
Sign In
@dropthis/mcp

@dropthis/mcp

Official
by dropthis-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a drop's view analytics

dropthis_analytics
Read-only

Get approximate view analytics for a drop by its drop ID. Returns view counts and traffic breakdown by country, referrer, and day based on your plan.

Instructions

Approximate view analytics for one drop, by its drop_… id. Gated by the analytics capability: Free returns feature_not_in_plan (403, needs Keep); Keep (view_count) returns views + truncated only; Pro+ (full) also returns byCountry / byReferer / daily. Counts are best-effort — captured fire-and-forget at the edge, so treat them as an approximate signal, not exact human visits. Requires drop_id (id-only — for a public URL or slug call dropthis_resolve first). Use when the user asks how many views / how much traffic a drop got.

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": {
      "drop_id": "<drop_id>"
    },
    "name": "dropthis_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
drop_idYesThe `drop_…` id of the drop whose analytics to read (id-only — a URL or slug is rejected; call dropthis_resolve to turn a public URL/slug into its id first).

Output Schema

NameRequiredDescriptionDefault
dailyNoDaily view series [{date, views}] — full (Pro+) analytics only; null on view_count.
viewsYesApproximate total canonical-view count (best-effort).
byCountryNoTop countries [{key, views}] — full (Pro+) analytics only; null on view_count.
byRefererNoTop referer hosts [{key, views}] — full (Pro+) analytics only; null on view_count.
truncatedNoTrue when the event set exceeded the read cap and the figures are a lower bound.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.37.0

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond the readOnlyHint annotation, disclosing that counts are 'best-effort — captured fire-and-forget at the edge, so treat them as an approximate signal, not exact human visits.' It also details plan-gated responses (feature_not_in_plan, views+truncated, byCountry/byReferer/daily), which is crucial behavioral context.

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 dense but well-structured: purpose first, then capability tiers, accuracy caveat, parameter prerequisite, and usage trigger. Every sentence contributes unique information, with no filler or restatement. Length is justified by the tool's complexity.

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?

The description covers the usage scenario, plan-based return variations, accuracy limitations, and the prerequisite resolve step. With an output schema present, it does not need to list return fields, and it adequately handles error cases (feature_not_in_plan). Complete for a read-only analytics tool.

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 covers the only parameter (drop_id) fully, including the id-only requirement and the resolve alternative. The description essentially repeats this, adding no new semantic information beyond the schema. Baseline 3 applies due to high schema coverage.

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's function: 'Approximate view analytics for one drop, by its `drop_…` id.' It uses a specific verb ('get' from title, but more precisely 'read analytics') and resource ('view analytics for a drop'), and distinguishes from siblings by specifying id-only usage and pointing to dropthis_resolve for URL/slug inputs.

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?

Explicit guidance is provided: 'Use when the user asks how many views / how much traffic a drop got.' It also tells the agent to call dropthis_resolve first for public URLs/slugs, and explains capability-based limitations (Free vs Keep vs Pro+) that affect when the tool is usable.

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