WEIR AI

Search possible mentions of a name

search_mentions

Read-onlyIdempotent

Search WEIR AI's supported web and social media sources for potential mentions associated with a person's name. The person does not need an existing WEIR identity or license. Results are candidate matches, not verified identification or evidence of infringement. Required: name (a person's full name; the same name checks as weir.ai/search apply). Optional: limit 1-50. When the user has connected their WEIR AI account, results follow their own plan; without a connection some results are hidden (redacted:true). Give the user results_url to see what their plan allows. Never claim a match is the person. [Public, no account needed]

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

Input Schema

Name	Required	Description	Default
`name`	Yes	The person's full name, e.g. 'Jane Doe'.
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, yet the description adds substantive behavior beyond them: results are candidate matches rather than verified identification, results follow the caller's plan when connected, and some results come back redacted:true otherwise. It also tells the agent to surface results_url and never assert a match is the person, which is genuine operating 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?

Front-loads purpose, then constraints, then result semantics and the redaction caveat, with no filler sentences. The parenthetical "[Public, no account needed]" and the plan/redaction note both carry real decision value.

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?

No output schema exists, so the description carries the return-value burden and does so: it explains that results are candidate matches, that hidden results appear as redacted:true, and that results_url shows plan limits. For a two-parameter read tool this is complete enough to call correctly without further inference.

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 coverage is only 50% (limit has bounds but no description), so the description has to compensate, and it does: it clarifies that name is a person's full name governed by the same matching as weir.ai/search, and states the 1-50 limit range. The limit restatement is largely redundant with the schema's minimum/maximum/default, which keeps it from a 5.

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 ("Search ... supported web and social media sources for potential mentions") plus the scope anchor "associated with a person's name". It also distinguishes itself from the license-scoped siblings by noting the person "does not need an existing WEIR identity or license", which separates it from list_license_mentions and check_identity.

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?

Gives clear preconditions: only a name is required, no account or license is needed, and the same name checks apply as on weir.ai/search. It does not explicitly name a sibling alternative or a "do not use this for X" exclusion, so it stops just short of full routing guidance.

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

All WEIR AI 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?