Skip to main content
Glama

Get my dashboard link

getTalentDashboardLink
Read-onlyIdempotent

Returns the exact Clera dashboard URL for one section of the candidate's own dashboard. One link per request, the one that answers the question; "my dashboard" means home. Commands: list: every link, for when you are unsure which command fits; for you only, never sent to the user. home: overview with profile setup and the top matches. matches: the roles Clera matched, with like, pass and the role questions. applications: the job tracker ("Tracker" in their menu): their own applications with tailored resumes and cover letters per job, plus every Clera intro except withdrawn ones (listMyPipeline says each intro's column). jobs: the wide external job board (searchJobs, saveJob and passJob work on the same data). interview_prep: prep for their next scheduled interview: what the interviewer looks for, stories to tell, a salary line and questions to ask; with none booked, the general interview guides. resume: the resume builder with live preview, plus upload, replace or pick the primary resume. upload_resume: the resume page with the upload box open, for a file on their computer; a Google Drive or iCloud share link goes through importResumeFromLink instead. preferences: salary, location, work environment, visa, roles and blocked companies. voice_intro: the Me overview, where the candidate records a 90-second voice intro, replays it and corrects Clera's transcript. It needs their microphone, so only they can do it. referral: the referral link, invited friends and earnings. worth: the salary calculator. roast: the profile roast, which needs a PDF upload. perks: partner perks and discounts. interview: interview invitations and feedback. account: login email, profile photo, and the channels Clera reaches them on (email, WhatsApp, iMessage). deleteMyAccount covers account deletion. This tool is the only source of Clera dashboard links: never construct, guess, shorten or modify a getclera.com URL; copy it from here verbatim.

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

Input Schema

NameRequiredDescriptionDefault
commandYesWhich dashboard link to return. Run list first to see the full menu.

Output Schema

NameRequiredDescriptionDefault
linkYes
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds genuinely new behavior: this is the only source of Clera dashboard links, URLs must be copied verbatim and never constructed or shortened, and inputs/results are logged for support. It does not describe pagination or what happens with an invalid command, so it stops short of 5.

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 purpose and the hard constraint about never constructing URLs, then a scannable one-line-per-command list. Every line carries information, though the block is long and a few entries (roast, perks, worth) sit far from the tool's central purpose, slightly diluting scanability.

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 single-enum-parameter read tool with an output schema already describing returns, nothing an agent needs is missing: purpose, all enum semantics, prerequisite conditions, sibling routing, and the verbatim-URL constraint are all present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum is self-documenting, but the schema only says 'Which dashboard link to return'. The description supplies the actual meaning of all 16 enum values — what each section contains, which ones need special prerequisites (voice_intro needs a microphone, roast needs a PDF), and the fallback behavior for interview_prep when nothing is booked. That is real semantic lift beyond the schema.

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?

Opens with a specific verb+resource: returns the exact dashboard URL for one section of the candidate's *own* dashboard. The phrase 'my dashboard means home' and the explicit 'candidate's own' framing separate it from the recruiter-side getDashboardLink sibling, and the command menu shows precisely what is being addressed.

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?

Explicit when-to-use guidance per command (e.g. 'list: every link, for when you are unsure which command fits'), plus concrete exclusions that route to alternatives: 'a Google Drive or iCloud share link goes through importResumeFromLink instead' and 'deleteMyAccount covers account deletion'. It also states 'list' is for the agent only, never sent to the user.

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