Skip to main content
Glama

Trumpet: find creators

trumpet_find

Trumpet™: one page of up to 20 micro creators (3,000 to 150,000 followers or subscribers by default) on youtube, tiktok, instagram or twitter, found on influencers.club by niche (a line on who they are and who watches them, written from the product's buyers) and sized on the platform's own field; keywords for their bios; brandDeals true for those who did brand deals before. Returns the new ones (each with a key, handle, name, followers, engagement) and the total that match. $1.20 a page, charged only when creators come back: ask the founder first.

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": {
      "platform": "<platform>",
      "niche": "<niche>"
    },
    "name": "trumpet_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNo
minNo
pageNo
nicheYesWho the creators are and who watches them, from the product's buyers
keywordsNoShort single words in their bios
platformYes
brandDealsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnly=false, openWorld=true, destructive=false, so the real value is the description's disclosure of pricing ($1.20 a page, charged only when creators come back) and the approval requirement. It also discloses deduplication behavior ('Returns the new ones') and the default 3,000–150,000 follower band, which the annotations do not cover.

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

Conciseness3/5

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

Almost all content is packed into a single run-on sentence with parentheticals, and the price plus approval warning sit at the very end where they are easiest to miss. Every fact earns its place, but the packaging makes it slow to parse for a time-sensitive decision.

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?

With no output schema, the description covers the return shape (key, handle, name, followers, engagement) plus the total match count, and it discloses cost and dedup behavior. Missing are pagination semantics for the page parameter and any statement of what an empty or failed lookup looks like.

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 29% (two of seven params documented), so the description must compensate, and it largely does: it names the default min/max band, defines keywords as bio terms, defines brandDeals as prior brand work, and ties niche to 'who they are and who watches them'. It never explains the page parameter or the 0–20 bounds, and 'sized on the platform's own field' is opaque.

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 specific verb and resource: finds one page of up to 20 micro creators on youtube/tiktok/instagram/twitter by niche, with the default follower band and return fields spelled out. It never names the sibling tools 'trumpet' or 'trumpet_contact', so the agent must infer that 'the key' in the response is what feeds those tools.

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?

Usage context is implied rather than stated: it is for prospecting micro creators by niche and bio keywords, and 'ask the founder first' signals a spend-approval gate. There is no explicit when-to-use versus trumpet_contact or trumpet, and no guidance on paging strategy or when a niche is too broad.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources