GetMattered

Create Resume Builder Draft

getmattered_create_resume_draft

Creates a private builder draft with the given text as its summary section. It creates no PDF. Needs a paid plan.

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": {
      "summary_text": "<summary_text>"
    },
    "name": "getmattered_create_resume_draft"
  }
}

Input Schema

Name	Required	Description
`template`	No	Resume template style: classic (default), modern or minimal.
`make_public`	No	When true, publishes a public share link to the draft. Anyone with the link sees it INCLUDING its contact details. Defaults to false (private).
`summary_text`	Yes	The text to save as the draft's summary section, 50 to 2,000 characters, as the user wrote or approved it.

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 8, 2026

changedInput schema / properties / make_public / description

Previous value: -"Publish a public share link to the draft. Anyone with the link sees it INCLUDING its contact details. Defaults to false (private). Only set true when the user explicitly asks to share it."New value: +"When true, publishes a public share link to the draft. Anyone with the link sees it INCLUDING its contact details. Defaults to false (private)."

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.2/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=false), and the description adds non-obvious context: the draft is private by default, no PDF is produced, and a paid plan is required. It does not explain what happens to an existing draft or the effect of the make_public flag, but the added prerequisites are meaningful over annotations.

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?

Three short sentences, each carrying distinct information: the action, the key exclusion (no PDF), and the prerequisite. Front-loaded and free of repetition.

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 and full parameter coverage, the description only needed to cover purpose, side effects, and prerequisites, which it does. It leaves minor ambiguity about draft replacement behavior, but nothing an agent needs to invoke it correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so template, make_public, and summary_text are already well documented in the schema. The description only restates the summary_text role and adds no format or defaulting detail beyond the schema, so baseline 3 applies.

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 ('Creates a private builder draft') and names the exact input it consumes ('the given text as its summary section'). The clause 'It creates no PDF' sharply distinguishes it from sibling tools like getmattered_get_resume_pdf_link and share_resume_pdf.

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

Usage Guidelines4/5

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

Gives a clear prerequisite ('Needs a paid plan') and an implicit exclusion (not for PDF generation), which steers agents away from misusing it. It stops short of naming the sibling to use when an actual PDF is wanted, so the when-to-use routing is clear but not fully explicit.

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.