SideShift Scanner

recommend_creators_for_brief

Ranks active creators by relevance to your brief or format tags, providing a rationale for each match. This helps you identify suitable UGC creators quickly.

Instructions

Rank active creators for a brief or set of format tags, with rationale for each match.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recommend_creators_for_brief"
  }
}

Input Schema

Name	Required	Description	Default
`n`	No
`brief_text`	No
`format_tags`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only adds 'active creators' and 'rationale for each match' but fails to state whether the operation is read-only, what 'active' means, how ranking is determined, or any side effects. This is a significant gap for a tool that likely performs complex logic.

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 a single sentence that is front-loaded with the core action and includes the key input types and output feature. Every word contributes meaning without redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description is too sparse for a tool with 3 optional parameters and no schema-level explanations. It lacks information on parameter interplay, what 'active' means, or how ranking works, making it incomplete for an agent to use correctly, especially given the presence of overlapping siblings like top_performers.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions 'brief' and 'format tags' but does not explain the n parameter, the relationship between brief_text and format_tags, or whether they are alternatives or combined. The default behavior when values are null is also undocumented.

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 a specific action ('Rank active creators') with a defined input ('a brief or set of format tags') and an expected output ('rationale for each match'). This distinguishes it from siblings like list_creators (no ranking) and top_performers (likely performance-based ranking without rationale).

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?

The phrase 'for a brief or set of format tags' implies the use case, but it does not explicitly state when to use this tool over alternatives such as top_performers or list_creators. There is no mention of exclusions or prerequisites (e.g., whether both brief_text and format_tags can be used together).

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

Deploy Server