Skip to main content
Glama

SocialCaptain Creator Tools

Instagram and TikTok username ideas

username_ideas
Read-onlyIdempotent

Username ideas for Instagram or TikTok from a name, keywords and a niche. Every idea follows the platform's rules (Instagram: up to 30 characters, lowercase letters, numbers, periods and underscores; TikTok: 2 to 24 characters, letters, numbers, underscores and periods). Give at least one of name, keywords or niche. Whether a handle is free on the platform is not checked.

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

Input Schema

NameRequiredDescriptionDefault
nameNoA person's or brand's name, for example 'Anna Rivera'.
seedNoOptional: another number gives another set of ideas. The same input and seed always give the same ideas.
countNoHow many ideas. Default 12.
nicheNoThe account's niche.
keywordsNoUp to 5 words that describe the account.
platformNoDefault instagram.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds genuine value by spelling out the platform character/character-set rules and, importantly, disclosing the limitation 'Whether a handle is free on the platform is not checked' — a caveat an agent could otherwise misrepresent to a user.

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?

Three sentences, front-loaded with purpose, then rules, then the input constraint and the key limitation. No filler and no repetition of the title.

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 and six optional parameters, the description covers purpose, input precondition, platform constraints and the availability caveat. It does not describe the shape of the returned ideas (e.g., list of strings, per-platform split), which is the one remaining gap, but nothing critical for correct invocation is missing.

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 adds meaning beyond the schema by stating the at-least-one-of constraint across name/keywords/niche, which the schema does not encode since no parameters are marked required. It also restates the platform rule differences, reinforcing the enum implications.

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?

Names a specific verb+resource ('Username ideas for Instagram or TikTok') and the inputs that drive them ('from a name, keywords and a niche'). It is clearly distinct from all siblings, which are calculators/statistics/fonts tools, so an agent can route to it without opening a 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?

States a real precondition: 'Give at least one of name, keywords or niche.' Combined with the platform-scoped phrasing, an agent knows the context in which the tool applies. It stops short of naming alternatives or explicit when-not-to-use cases, so it does not reach a 5.

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