Spytrend

Get usage / quota

get_usage

Read-onlyIdempotent

Return the caller's current MCP quota: plan, tokens used, remaining and limit (free starter = 500 tokens total forever; paid plans = 40,000/month ≈ 2,000 default-page searches; Enterprise = personal limit via support). Token costs: 1 per delivered result (an ad/webmaster/advertiser row, a trends row, an entity card), ordinary ad media = 1, multilang-upload ad opening = 50, creative media = 10, TikTok row = 100. Each opening call is billed separately. You pay only for results actually delivered (short pages auto-refund). This call is FREE — it consumes no quota.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`plan`	No
`used`	No
`error`	No	Present only when isError is true: machine-readable failure. The human explanation stays in content.
`limit`	No
`params`	No	Request parameter echo: applied = parameters that shaped this result; normalized = parameters rewritten before applying (alias, type coercion, resolved id); ignored = parameters that were accepted but NOT applied, with the reason.
`window`	No
`reset_at`	No
`remaining`	No
`unlimited`	No
`server_version`	No
`multilang_ad_open_tokens`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 25, 2026

addedOutput schema / properties / error

Added value: +{
+  "description": "Present only when isError is true: machine-readable failure. The human explanation stays in content.",
+  "properties": {
+    "code": {
+      "description": "fine-grained, stable failure code (e.g. invalid_arguments, backend_busy)",
+      "type": "string"
+    },
+    "kind": {
+      "description": "failure class: invalid_argument, not_found, permission_denied, unauthenticated, quota_exceeded, rate_limited, temporarily_unavailable, unavailable_until_ready, unsupported, internal",
+      "type": "string"
+    },
+    "message": {
+      "description": "the same human text as content[0]",
+      "type": "string"
+    },
+    "outcome": {
+      "description": "activity-feed outcome class",
+      "type": "string"
+    },
+    "param": {
+      "description": "the request parameter the failure is about, when known",
+      "type": "string"
+    },
+    "retry_after_seconds": {
+      "description": "wait this long before retrying",
+      "type": "integer"
+    },
+    "retryable": {
+      "description": "true when repeating the SAME call can succeed (after retry_after_seconds when present)",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / params

Added value: +{
+  "description": "Request parameter echo: applied = parameters that shaped this result; normalized = parameters rewritten before applying (alias, type coercion, resolved id); ignored = parameters that were accepted but NOT applied, with the reason.",
+  "properties": {
+    "applied": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "ignored": {
+      "items": {
+        "properties": {
+          "param": {
+            "type": "string"
+          },
+          "reason": {
+            "type": "string"
+          },
+          "to": {
+            "description": "the parameter it was applied as, when renamed",
+            "type": "string"
+          },
+          "value": {
+            "description": "the value actually applied, when rewritten",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "normalized": {
+      "items": {
+        "properties": {
+          "param": {
+            "type": "string"
+          },
+          "reason": {
+            "type": "string"
+          },
+          "to": {
+            "description": "the parameter it was applied as, when renamed",
+            "type": "string"
+          },
+          "value": {
+            "description": "the value actually applied, when rewritten",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "plan",
-  "used",
-  "remaining",
-  "limit",
-  "window",
-  "multilang_ad_open_tokens"
-]

Changed2 schema fields changedSep 9, 2026

addedOutput schema / properties / multilang_ad_open_tokens
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / required

Previous value: -[
-  "plan",
-  "used",
-  "remaining",
-  "limit",
-  "window"
-]New value: +[
+  "plan",
+  "used",
+  "remaining",
+  "limit",
+  "window",
+  "multilang_ad_open_tokens"
+]

First observedSep 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, and the description adds meaningful behavior beyond those hints: the call is free, consumes no quota, token costs are itemized for various result types, and short pages auto-refund. This gives the agent a precise cost model for planning subsequent calls. No contradiction with annotations.

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?

Although lengthy, every sentence carries actionable cost or quota information: plan limits, per-result token costs, the free nature of the call, and refund behavior. The essential quota summary is front-loaded, and the cost details support an agent's decision-making without redundancy.

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 full operational context an agent needs: what the tool returns, plan tier differences, billing of results, and the fact that the call itself is free. An output schema exists for the return value, so return-format details are not the description's responsibility. Nothing material is missing.

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

Parameters4/5

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

The tool has zero parameters, so there is no parameter burden for the description to carry. Schema coverage is trivially 100%. Per the baseline for zero-parameter tools, the description is not required to explain parameters, and it does not need to.

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 opens with a specific verb and resource: 'Return the caller's current MCP quota' followed by exactly what is included (plan, tokens used, remaining, limit). It is unmistakably distinct from sibling tools like get_ads_analytics or search_* tools, which retrieve data rather than quota state.

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 provides strong contextual usage guidance by explaining plan-specific quotas (free vs paid vs Enterprise) and clarifying that the call itself is free and consumes no quota. It does not explicitly name alternatives or state when not to use it, but the tool's unique purpose makes the intended context clear.

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

All Spytrend tools Inspect

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.