GetMattered

Share Resume PDF Publicly

getmattered_share_resume_pdf

Idempotent

Turns on a public link to the resume PDF. Anyone with it can read the contact details.

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_share_resume_pdf"
  }
}

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

A3.9/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations by disclosing that the resulting link is public and that anyone with it can read the contact details. This is important privacy information for a mutating, open-world operation. It does not explain whether the link can later be revoked or disabled, but the annotations already indicate idempotence and non-destructiveness.

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?

The description is two short sentences with no wasted wording, and the core action is front-loaded. It efficiently conveys both the operation and its privacy implication.

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 zero-parameter tool with an output schema and rich annotations, the description covers the essential action and the public exposure of contact details. The main remaining gap is revocation behavior, but the definition is otherwise complete for correct invocation.

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 semantics burden on the description. The empty input schema is fully consistent with the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: turning on a public link to the resume PDF. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling get_resume_pdf_link, which likely retrieves the link rather than enabling sharing.

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 phrase 'Turns on a public link' implies the tool should be used when public sharing is desired, but there is no explicit when-to-use guidance. It also does not mention the alternative get_resume_pdf_link or clarify when not to use this tool.

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.