Skip to main content
Glama

Create Resume Builder Draft

getmattered_create_resume_draft

Starts a private resume builder draft using your supplied summary text, with an optional template and public share link. It generates no PDF and requires a paid plan.

Instructions

Creates a private resume 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

NameRequiredDescriptionDefault
templateNoResume template style: classic (default), modern or minimal.
make_publicNoWhen true, publishes a public share link to the draft. Anyone with the link sees it INCLUDING its contact details. Defaults to false (private).
summary_textYesThe text to save as the draft's summary section, as the user wrote or approved it.

Output Schema

NameRequiredDescriptionDefault
urlYesThe private link: the builder draft, or the documents page of the resume on file. It needs the user's sign-in.
templateYesThe draft's template. Null when no draft was created.
publicUrlYesThe public share link. Null unless sharing was asked for and succeeded.
setupStepNoPresent while account setup is open: the first setup step.
documentIdNoThe resume document whose PDF the link opens, when no draft was created.
resumeBuildIdYesThe 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.

  1. Changed1 schema field changedv1.20.1
    • changedInput schema / properties / summary_text / description
      Previous value: -"The text to save as the draft's summary section, 50 to 2,000 characters, as the user wrote or approved it."New value: +"The text to save as the draft's summary section, as the user wrote or approved it."
  2. Changed2 schema fields changedv1.13.2
    • 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)."
    • addedOutput schema / properties / setupStep
      Added value: +{
      +  "description": "Present while account setup is open: the first setup step.",
      +  "type": "string"
      +}
  3. Addedv1.10.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare the write/open-world profile, and the description adds two things the annotations cannot: the result is a private draft and no PDF is generated, plus a billing precondition. It does not address what happens on repeated calls (annotations say non-idempotent), leaving duplicate-creation risk implicit, which keeps it from a 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?

Three short sentences, front-loaded with the core action and followed by the two caveats that matter most (no PDF, paid plan). No filler, though the sentence fragments read slightly telegraphic rather than fully polished.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 documentation in the schema, the description needn't explain return values, and it correctly covers the PDF and plan caveats. What it omits is the creation-semantics angle — whether each call makes a new draft and what happens to prior drafts — which matters for a non-idempotent write tool.

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 coverage is 100% and every parameter already has a rich description including the make_public visibility warning and template enum defaults. The description's 'as its summary section' and 'private' mostly restate what the schema fields already say, so it adds little semantic value beyond the baseline.

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 uses a specific verb and resource (creates a resume builder draft) and states exactly what content goes into it (the given text as the summary section). The clause 'It creates no PDF' carves it apart from the sibling that produces PDFs, giving the agent a real discriminator, though no sibling is named outright.

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?

'Needs a paid plan' is a genuine precondition the agent can act on, so usage context is implied rather than absent. There is still no explicit when-to-use versus when-not guidance, nor a pointer to alternatives like optimizing or scoring a resume, which an agent choosing among many resume tools would want.

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