CollabPls

search_creators

Find CollabPls creators by city, name/handle, STD-tested window, or verification. Returns SFW public profiles + profile URLs. Prefer reachable creators for outreach.

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": "search_creators"
  }
}

Input Schema

Name	Required	Description
`q`	No	Name, slug, or X handle fragment
`city`	No	City or location fragment, e.g. Los Angeles
`limit`	No	Max results (1-50, default 20)
`tested_days`	No	Only creators with std_tested_at within N days
`verified_only`	No	Require X verified or CollabPls ID verified
`reachable_only`	No	Only creators with a real email on file

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure alone. It does disclose the return shape ('SFW public profiles + profile URLs'), which is valuable, but says nothing about permissions, pagination behavior, rate limits, or what filtering by 'reachable' actually costs. Adequate but not rich.

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?

Two tightly packed sentences with zero waste: the first front-loads the capability and filter axes, the second adds the return shape and the outreach preference. Every clause earns its place.

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?

For a 6-param read-style search with no output schema and no annotations, the description covers capability, filter axes, and return type, which is close to complete. It could still note the result cap default or the interplay between filters to be fully self-sufficient.

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 description coverage is 100%, so the schema already documents all six parameters in detail; this is the baseline case. The description adds no syntax, edge-case, or default information beyond the schema, so it cannot exceed the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource ('Find CollabPls creators') and lists the axes by which finding works (city, name/handle, STD-tested window, verification). It does not name or distinguish itself from siblings like find_overlaps or get_profile, so it stops short of the top score.

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 closing clause 'Prefer reachable creators for outreach' implies an intended use case, but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as find_overlaps or get_profile for related lookups.

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

All CollabPls 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?