Skip to main content
Glama

Apply as a ProductClank scout

apply_as_scout

Start a scout application for the signed-in user. Scouts are trusted people in a niche (growth people, marketers, fractional CMOs, founders) who earn when a founder they introduce becomes a client. Free; the user can be brand new. Ask for at least an X handle or a LinkedIn URL (a site and free-text references help). If they came from another scout's invite link or gave you an invite code (looks like ERAN-7K2Q), pass it as invite_code. This reads ONLY the public profiles they give and drafts an editable profile; it takes about 30-150 seconds and this tool waits up to ~75s. Then show the user the draft (headline, niches, audience, who they can reach, tone, never-pitch list) and what was found, take their edits, ask how they want to work (channels: public_replies / dms / intros; deals per day: 1 / 3 / 5), and call submit_scout_application. Nothing is used until they submit, and a person at ProductClank reviews every scout. Call get_scout_application FIRST if they may have applied before: a rebuild clears an earlier submit. Max 3 builds per day.

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

Input Schema

NameRequiredDescriptionDefault
site_urlNoPersonal site, portfolio or newsletter.
x_handleNoThe user's X handle, with or without @.
referencesNoFree text: past clients, communities, newsletters, portfolio links.
invite_codeNoAnother scout's invite code, if the user has one.
linkedin_urlNolinkedin.com/in/<name>

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that only public profiles are read, that a draft (not a live profile) is produced, the 30-150s runtime with a ~75s wait cap, that nothing is used until submit, that a human at ProductClank reviews, that a rebuild clears an earlier submit, and the 3-builds-per-day limit. The rebuild-clears-submit note is a side effect consistent with destructiveHint=false being an annotation about the resource not being destroyed outright.

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?

Front-loaded with the action and definition, and nearly every sentence carries operational value. It is a dense single block, though, mixing purpose, input rules, timing, and a multi-step follow-up workflow; slight structure (or trimming the payoff explanation) would make it easier to scan.

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?

For a multi-step, long-running, human-reviewed application flow with no output schema, the description supplies everything an agent needs: expected duration and wait behavior, the draft fields to surface to the user, the follow-up questions to ask (channels, deals per day), and the rate limit.

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 100%, so the baseline is 3, but the description adds real meaning: invite_code has a recognizable shape (ERAN-7K2Q), and the soft requirement that at least one of x_handle/linkedin_url be supplied resolves the ambiguity created by zero required parameters. It also frames site_url and references as optional corroboration rather than primary identifiers.

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?

"Start a scout application for the signed-in user" gives a specific verb and resource, and the following sentence defines what a scout is and what the user earns. It clearly separates this build step from submit_scout_application and get_scout_application, so an agent can pick it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to call it (new or brand-new scout, free), what inputs are needed at minimum (X handle or LinkedIn URL), how to handle an invite code, and that get_scout_application should be called FIRST if the user may have applied before. It also names the mandatory follow-up (submit_scout_application) and hands over the remaining decision points.

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.