Suara

Apply to Suara's partner program

apply_as_partner

Use this only when a content or UGC creator, an educator or coach, an owner-creator or a social media manager wants to apply to Suara's partner program (https://trysuara.com/partners). It is commission-only: partners refer small businesses to Suara and earn a share of what each referred business pays: the first 20 partners get 30% every month for as long as that business keeps paying (no 12-month cap), and partners after the first 20 get 25% for 12 months per business. Social media managers can refer their current clients and businesses they can't take on; each business signs up through the partner's link. Not for a business that wants Suara for itself, and nobody can refer their own business or a business they run. Partner rules: say you earn a commission (#ad, #affiliate or the platform's paid partnership label, and in words); only say what's true about Suara, no promised results; no spam or link-drops in other businesses' comments; no paid ads on the Suara name; no coupon or deal sites; don't pretend to be Suara staff. Before calling: ask for each detail (don't guess any), then show the person everything you will send plus the rules, and call only after they explicitly confirm. Set confirmed to true only then. It sends the application to the Suara team; nothing else happens and no account is created.

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": {
      "name": "<name>",
      "email": "<email>",
      "country": "<country>",
      "channel": "<channel>",
      "audience_size": "<audience_size>",
      "audiences": "<audiences>",
      "role": "<role>",
      "how_you_will_share": "<how_you_will_share>",
      "handle": "<handle>",
      "agrees_to_rules": "<agrees_to_rules>",
      "confirmed": "<confirmed>"
    },
    "name": "apply_as_partner"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The person's full name
`role`	Yes	What they do
`email`	Yes	Their email, where Suara will reply
`handle`	Yes	The handle they want in their link (trysuara.com/app/start/?src=creator-<handle>): 2 to 30 lowercase letters, numbers, _ or -
`channel`	Yes	Their main channel link, e.g. instagram.com/theirname, a TikTok, YouTube, newsletter or website
`country`	Yes	Where they are. 'Another country' if theirs isn't listed.
`business`	No	Their own business's Instagram or website if they'd like Suara for it, optional
`audiences`	Yes	Who their audience is (pick any that fit)
`confirmed`	Yes	True only after they saw every detail above and explicitly said to send it
`other_links`	No	Other channels or links, optional
`audience_size`	Yes	Rough audience size
`agrees_to_rules`	Yes	True only if they said they'll disclose the commission and follow the partner rules
`how_you_will_share`	Yes	How they'd share Suara, in their words: a reel, a newsletter, a talk, a word with clients...

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world mutation. The description adds important context beyond them: it sends the application to the Suara team, nothing else happens, no account is created, and confirmed must be true only after the person explicitly confirms.

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?

The description is long, but the complexity and consent requirements justify most of the content, and it is front-loaded with the core usage rule and exclusions. It could be more scannable with structure, and some commission/rule detail is dense, but it is not padded.

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?

Given the 13-parameter application form, mutation annotations, and no output schema, the description is complete enough: it explains what the tool does, when to use it, the confirmation gate, and what happens after submission. No critical calling context is missing.

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 13 parameters, including confirmed and agrees_to_rules. The description adds workflow context around confirmation but does not materially extend per-parameter semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: apply to Suara's partner program. It also names the target users (content/UGC creators, educators/coaches, owner-creators, social media managers) and explicitly excludes businesses that want Suara for themselves, making it clearly distinct from sibling tools.

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?

It gives explicit when-to-use guidance, when-not-to-use exclusions ('Not for a business that wants Suara for itself'), and a required pre-call workflow: ask for each detail, show the person everything plus the rules, and call only after explicit confirmation. This leaves little to inference.

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

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