MentionedOn Visibility and Website Fixes

Read drafted articles

list_articles

Read-onlyIdempotent

Needs a connected MentionedOn account. Use to fetch drafted articles: returns up to 20 recent drafts with the questions each targets, the buyer it was written for and the Markdown (first 4,000 characters), plus this month's usage. Needs businessId. Read-only; new drafts are made in MentionedOn and count against the plan's monthly allowance.

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": {
      "businessId": "<businessId>"
    },
    "name": "list_articles"
  }
}

Input Schema

Name	Required	Description	Default
`businessId`	Yes	Business id returned by list_monitored_businesses.

Output Schema

Name	Required	Description	Default
`articles`	Yes
`reportUrl`	Yes
`businessId`	Yes
`limitations`	Yes
`usedThisMonth`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it adds concrete operational context: an auth/account prerequisite, a 20-item result cap, a 4,000-character truncation of Markdown, inclusion of monthly usage, and the fact that new drafts consume the plan's monthly allowance. The truncation and cap details are exactly the kind of behavior an agent cannot infer from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Prerequisite, action, return shape, and caveat arrive in that order in a tight paragraph with no padding. The only mild redundancy is 'Needs businessId', which repeats what the schema already enforces.

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?

An output schema exists, yet the description still supplies the practical payload details (cap, truncation, usage figures) plus auth and quota context. For a single-parameter read tool, nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% and the schema already documents businessId as 'Business id returned by list_monitored_businesses'. The description only restates 'Needs businessId' without adding format, sourcing, or edge-case meaning, so it sits at the baseline for a fully documented single parameter.

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 uses a specific verb and resource ('fetch drafted articles') and immediately enumerates what comes back: up to 20 recent drafts, the questions each targets, the buyer, and the Markdown excerpt. It also separates this from the drafting sibling by stating 'new drafts are made in MentionedOn', so an agent knows this tool only reads.

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?

It states a clear precondition ('Needs a connected MentionedOn account') and an explicit use case ('Use to fetch drafted articles'), and implicitly excludes creation by pointing elsewhere for making drafts. It stops short of naming an alternative tool or stating when-not-to-use conditions.

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

All MentionedOn Visibility and Website Fixes 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.

Resources

Need Help?