Skip to main content
Glama

Seenly

Get Seenly signup link

get_signup_link
Read-only

Return a Seenly signup URL for a job seeker. The link opens the start page so the seeker can create their own account in the browser. Pass the calling product or assistant name as agent_name so signups can be attributed. Never create the account yourself.

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

Input Schema

NameRequiredDescriptionDefault
agent_nameNoName of the calling assistant or product, for example claude, chatgpt, or career-coach.

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 declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the link resolves to a start page where the human, not the agent, completes account creation, and agent_name exists for attribution tracking. Minor gaps remain (link lifetime/one-time use, whether it can be regenerated).

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 short sentences, front-loaded with the return value, then behavior, then the parameter instruction. Nothing is redundant and the strongest constraint ('Never create the account yourself') lands last for emphasis.

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?

For a one-optional-parameter, no-output-schema tool with readOnly annotations, the description covers what it returns, how the flow proceeds, and the key prohibition. Only link validity details (expiry, reuse) are absent, which is a small gap given the tool's simplicity.

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% and the single parameter is optional, so the schema already handles the format. The description still adds value by explaining why agent_name should be passed ('so signups can be attributed'), turning a bare string field into a purposeful action.

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 verb and resource ('Return a Seenly signup URL for a job seeker') plus what the link does ('opens the start page so the seeker can create their own account'). An agent can immediately tell this apart from about_seenly or get_public_profile, which are informational lookups rather than link generators.

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 clear context for when to use it (obtaining a self-service signup link) and an explicit negative constraint: 'Never create the account yourself.' It does not enumerate named alternatives, but the exclusion plus the browser-based flow makes the intended usage unambiguous.

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