Skip to main content
Glama

AceRound AI Interview Copilot

create_resume_from_text

Create a new resume from text (for example a revised version of the user's resume) for interviews and Auto Apply. No file is produced and existing resumes are left as they are. Returns the new resume id. (Requires the user's sign-in with scope resumes:write.)

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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "create_resume_from_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesResume title
contentYesFull resume text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-open-world behavior. The description adds meaningful context beyond them: no file artifact is produced, existing resumes are untouched, the return value is the new resume id, and write access requires the resumes:write scope. That is solid added value, short only of any note about limits or failure modes.

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?

Four short statements: what it does, the disambiguation, the return value, the auth requirement — all front-loaded with zero filler. The parenthetical auth note is compact and earns its place.

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 simple two-parameter mutation with no output schema, the description covers the essentials an agent needs: the write semantics, the unchanged side effects on existing resumes, the returned id, and the scope requirement. Only explicit alternative routing 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 both parameters (title, content) are already documented with types and length bounds. The description only adds that content is full resume text via "from text," which is a marginal gain over the schema 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 opens with a specific verb+resource ("Create a new resume from text") and contrasts it behaviorally with a file-based alternative by stating "No file is produced." It does not name a sibling such as upload_resume or delete_resume directly, so an agent must infer the routing, but the create-vs-upload distinction is legible.

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?

"for interviews and Auto Apply" and the parenthetical example "a revised version of the user's resume" give implied use contexts. However, no explicit when-not condition or named alternative (e.g., upload_resume vs. this tool) is provided, so selection guidance is only partial.

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