Rankwise

Refresh content opportunities

refresh_opportunities

Destructive

Recompute the workspace's opportunity queue from its tracked questions and AI citation data, and look for new topics. Uses paid search and AI data, so it runs at most once every 10 minutes per workspace. Send a unique idempotency_key; retry with the same key.

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": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "refresh_opportunities"
  }
}

Input Schema

Name	Required	Description	Default
`idempotency_key`	Yes

Output Schema

Name	Required	Description	Default
`created`	Yes
`refreshed`	Yes
`discovered`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations establish the write/destructive/open-world profile; the description adds genuinely new context: the paid search and AI data sources, a concrete rate limit of once per 10 minutes per workspace, and idempotency-key retry behavior. It stops short of explaining what 'destructiveHint: true' actually destroys (e.g. whether the existing queue is replaced).

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?

Three sentences, no filler. The core action is front-loaded, followed by the cost/rate constraint and then the caller obligation, in descending order of importance.

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?

An output schema exists, so return values need no explanation. Sources, rate limit, and idempotency are all covered. The one remaining gap is the destructive behavior implied by annotations but never spelled out in prose.

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?

Schema description coverage is 0%, so the description carries the burden, and it does: it explains that the key must be unique, that it powers retry semantics, and that the same key should be reused on retry. Length/format constraints live in the schema, which is fine.

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?

States a specific verb and resource: 'Recompute the workspace's opportunity queue from its tracked questions and AI citation data, and look for new topics.' This clearly separates it from read-only siblings like list_opportunities and from the unrelated refresh_share_of_voice.

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

Usage Guidelines3/5

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

Gives operational guidance (paid data, at most once per 10 minutes per workspace) and retry semantics, but never says when to prefer this over alternatives such as list_opportunities or when a refresh is warranted. Usage is implied rather than explicitly routed.

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

All Rankwise 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.