Skip to main content
Glama

SeedViews

Approve the brief and start outreach

send_offers

Approves the brief and the opening message together, so outreach starts: SeedViews begins messaging real creators and sending them the paid offer. This reaches real people; confirm the brief and opening_message_preview with your person first. Optional brief, looking_for and opening_message are final edits; notify_url can be set here too. invite adds creators your person already works with (an email gets the offer at once). If the casting is not paid yet, nothing happens and the answer says which link your person must open to pay.

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

Input Schema

NameRequiredDescriptionDefault
briefNoFinal version of the brief, if it changed.
inviteNoCreators your person already knows, to add to this casting.
casting_idYesThe casting id that cast returned.
notify_urlNoOptional https address that gets a signed POST when a person has something to do or something changed (a video or payout awaiting approval with its deadline, a creator signed, the casting paid, opened or closed). If an approval is still waiting about 12 hours before its deadline, video.approval_reminder includes video_id and deadline (and payout_id when waiting on payment). The answer holds notify_secret once: keep it to check each delivery's seedviews-signature header.
looking_forNoWho to look for. Leave it out to use what SeedViews drafts from the store link.
casting_tokenNoThe casting_token that cast returned when it was called without an API key. Not needed with an API key.
opening_messageNoThe template of SeedViews' first message to each creator; leave it out to use the one drafted from the app and brief (opening_message in the answer). It must start with "Hi [name], [a line about one of their videos]. ", which SeedViews writes per creator, as it does any other [field] you add. Write [pay] where the pay goes: it is filled from the casting (opening_message_preview shows it). No other amount, no link, at most 700 characters, ending with one easy question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare that this is a non-read-only, open-world, non-destructive call; the description adds far more — real creators get contacted, the action is gated on payment with a no-op plus payment-link response, invites are emailed immediately, and notify_secret is returned once for signature verification. That is exactly the context an agent needs before a live, externally visible action.

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 core action and the human-confirmation warning, with supporting parameter notes following. The semicolon-heavy sentences pack multiple facts, but each carries real information and nothing reads as filler.

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?

A seven-parameter, nested-object, side-effecting tool with no output schema, and the description covers the missing pieces: the no-op path on unpaid castings, the returned payment link, the one-time notify_secret, and the immediate-email behavior of invite. An agent has enough to call this safely.

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; the description still adds meaning by framing brief, looking_for, and opening_message as final edits over drafted defaults, and by explaining that notify_url can be registered at this point. It does not re-explain invite or casting_token semantics beyond what the schema already covers.

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 action chain: approves the brief and opening message, then starts outreach by messaging creators with a paid offer. That is clearly distinct from cast (which creates the casting) and from pay_creator, so an agent can route without inspecting the schema.

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 the prerequisite (casting must be paid or nothing happens and a payment link is returned) and the human-approval protocol ('confirm the brief and opening_message_preview with your person first'). It also explains the invite variant for creators already known. It stops short of explicitly naming which sibling to call first, but the casting/money preconditions convey the sequence.

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