GetMattered

Share Resume PDF Publicly

getmattered_share_resume_pdf

Idempotent

Creates a public share link for the user's base resume PDF so anyone with the link can open it without signing in. Use only when the user explicitly asks to share their resume publicly.

Instructions

Turn on a public share link for the PDF of the user's base resume and return it. Anyone who has the link can open the resume, including the contact details on it, without signing in. Call it only when the user explicitly asks to share their resume publicly. Sharing can be turned off again on the user's GetMattered documents page. Nothing is sent to any employer and nothing is spent. Do not use it only to download the resume; use getmattered_get_resume_pdf_link. Next: give the user the link and remind them that it is public.

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.
`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.

Addedv1.10.2Oct 25, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description adds substantial context beyond the annotations: the link is public, anyone with it can view contact details without signing in, sharing can later be turned off, and nothing is sent to employers or spent. This is consistent with the annotations, including readOnlyHint=false, openWorldHint=true, and destructiveHint=false.

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 front-loaded with the core action and public-visibility consequence, then adds usage constraints, the alternative tool, and a post-call instruction. Each sentence contributes relevant guidance without repetition.

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?

Given the zero-parameter schema, existing output schema, and annotations, the description covers the action, privacy implications, usage boundaries, reversibility, and expected next step. Nothing essential for correct invocation appears to be missing.

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?

There are no input parameters, so there is no parameter semantics to explain beyond what the schema already conveys. The baseline for a zero-parameter tool is 4.

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?

The description states a specific verb and resource: turning on a public share link for the PDF of the user's base resume, and returning it. It also explicitly distinguishes this from getmattered_get_resume_pdf_link, so an agent can select the right tool without schema inspection.

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?

It gives a clear when-to-use condition ('only when the user explicitly asks to share their resume publicly') and a clear when-not-to-use case ('Do not use it only to download the resume'), naming the alternative tool to use instead.

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

Deploy Server