GetMattered

Get Resume PDF Link

getmattered_get_resume_pdf_link

Read-onlyIdempotent

Returns the private link to the PDF of the resume on file. Creates and shares nothing.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`url`	Yes	The private link: the builder draft, or the documents page of the resume on file. It needs the user's sign-in.
`template`	Yes	The draft's template. Null when no draft was created.
`publicUrl`	Yes	The public share link. Null unless sharing was asked for and succeeded.
`setupStep`	No	Present while account setup is open: the first setup step.
`documentId`	No	The resume document whose PDF the link opens, when no draft was created.
`resumeBuildId`	Yes	The new resume-builder draft. Null from getmattered_get_resume_pdf_link and getmattered_share_resume_pdf, which create no draft.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

changedOutput schema / properties / setupStep / description

Previous value: -"Set while account setup is open: the step to take first."New value: +"Present while account setup is open: the first setup step."

Changed1 schema field changedNov 6, 2026

addedOutput schema / properties / setupStep

Added value: +{
+  "description": "Set while account setup is open: the step to take first.",
+  "type": "string"
+}

AddedOct 25, 2026

TDQS

A4/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 'Creates and shares nothing' largely restates structured data. The one genuinely new piece of context is that the returned link is 'private', signalling a sensitive URL the agent should not redistribute; beyond that the description adds little behavioral depth.

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?

Two short sentences, with the core action front-loaded and the clarifying negative scope second. No filler or restated 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 an output schema present, the return value needs no prose, and annotations fully cover the safety profile. The only minor gap is not saying what happens when no resume exists on file, though 'on file' hints at that precondition.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the schema already closes that gap. Baseline 4 applies for a no-arg tool with nothing to mis-document.

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 private link to the PDF of the resume on file') and adds the negative scope 'Creates and shares nothing', which separates it from siblings like getmattered_share_resume_pdf and getmattered_create_resume_draft without needing to open either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The contrast with sharing and creation implies when this tool is the right pick (read-only link retrieval), but it never names the alternative tool or states an explicit when-not-to-use condition. Usage is inferable rather than stated.

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

All GetMattered 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.