Skip to main content
Glama

Get dashboard link

getDashboardLink
Read-onlyIdempotent

Returns the exact Clera dashboard URL for one section of this company's dashboard. One link per request, the one that answers the question; "my dashboard" means review. Commands: list: every link available to this company, for when you are unsure which command fits. For you only; never send the menu or several links to the user. review: the candidate review page. roleId scopes it to one role; talentId with it opens that candidate. pipeline: every candidate in process. roleId scopes it to one role; talentId with it opens that candidate. roles: the role list page. role_create: the create-a-role page. role_preview: the role as candidates will see it, with an edit button. Requires roleId. Hand it over after creating a role so the user can check how it reads. role_edit: the internal role editor. Requires roleId. role_public: the public job posting. Requires roleId; refuses when the role has no public posting. talent_search: the talent search page. Only available when Clera has enabled talent search for this company. settings_company: company profile settings, the public company information shown to candidates. settings_members: team member settings. invite true, optionally with email, opens the invite popup ready to send; Clera never sends team invites itself. settings_contacts: the company contacts settings page. settings_profile: the user's own personal profile, name and avatar only. This tool is the only source of Clera dashboard links. Never construct, guess, shorten or modify a getclera.com URL; copy the URL from this tool's output verbatim. There is no app.clera.io domain and no /org path.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "command": "<command>"
    },
    "name": "getDashboardLink"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNosettings_members: prefill the invite email. Only used when invite is true.
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
inviteNosettings_members: pass true to open the invite popup ready to send.
roleIdNoRole id for review and pipeline (optional scope), role_preview, role_edit, and role_public. Resolve ids with the job tool's list command.
commandYesWhich dashboard link to return. Run list first to see the full menu.
talentIdNoreview and pipeline: open this candidate's profile on arrival. Requires roleId. Use the talentId from listDropProfiles, listPendingIntroRequests or listPipeline.

Output Schema

NameRequiredDescriptionDefault
linkYes
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds substantial behavior: role_public refuses when there is no public posting, talent_search is availability-gated, Clera never sends team invites itself, and inputs/results are privately recorded. It also pre-empts hallucinated domains ('no app.clera.io domain and no /org path'), which is exactly the failure mode this tool must prevent.

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 rule and one-link-per-request constraint, then a scannable command list where each line earns its place. Slightly redundant phrasing ('the one that answers the question' / 'my dashboard' means review) and a trailing privacy line, but nothing is misleading or 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?

For a 13-command, 6-parameter tool with an output schema, everything an agent needs is present: every command is mapped to a purpose, required scoping parameters are called out, refusal conditions are noted, and return values are left to the output schema as appropriate.

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 baseline is 3, but the description adds real semantic layering on the command enum by explaining what each section actually shows and which parameters scope it (roleId scopes review/pipeline, talentId opens the candidate, invite+email opens the invite popup). It stops short of adding syntax detail for orgId beyond what the schema already says.

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 ('Returns the exact Clera dashboard URL for one section of this company's dashboard') and then enumerates all 13 selectable sections, so the agent knows precisely the scope of what it can get. It also distinguishes itself from URL-construction shortcuts by declaring itself the only source of dashboard links.

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?

Gives explicit routing: 'list' is for when you are unsure which command fits, 'role_preview' should be handed over after creating a role, and 'talent_search' only works when enabled. It also states anti-patterns that would otherwise be inferred wrongly: never send the menu or several links to the user, and never construct or shorten a getclera.com URL.

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