Skip to main content
Glama

create_resume

Create a blank resume from the profile header. Header links are LinkedIn, then the live Linkdfolio website (unless preferences.siteLinkInDocuments is false), then the profile links. Does not call a model and does not copy an existing resume. Returns the resume, its version, and an appUrl.

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

Input Schema

NameRequiredDescriptionDefault
titleNo
templateIdNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the exact header-link composition and ordering, the preferences.siteLinkInDocuments condition, the fact that no model is called, and that the response includes the resume, its version, and an appUrl. This is exactly the kind of behavioral detail the readOnly/destructive hints cannot convey.

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?

Front-loaded with the core action, then behavior, then return values in four tight sentences. The header-link ordering detail is useful but the densest sentence; nothing is wasted overall.

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?

Return values are covered in lieu of an output schema and behavior is well described, but for a two-optional-parameter creation tool the complete silence on title and templateId leaves a real gap an agent must guess through.

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

Parameters2/5

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

Schema description coverage is 0% and the description never mentions the two inputs, title and templateId, leaving their meaning and defaults entirely undocumented. The only named setting (preferences.siteLinkInDocuments) is not a parameter of this tool, so it does not compensate.

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 ("Create a blank resume from the profile header") and immediately distinguishes it from copying ("does not copy an existing resume"), which separates it from duplicate_resume among the siblings.

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?

The clause "Does not call a model and does not copy an existing resume" implies the when-not condition and points at duplicate_resume as the alternative for copying, but it never states a positive "use this when" trigger explicitly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources