Skip to main content
Glama

Resume Data Extraction from URL

extract_resume_data_from_url
Read-onlyIdempotent

Extracts structured candidate information from a resume or CV available at a publicly accessible document URL. Returns parsed resume data such as contact details, skills, employment history, education, and certifications.

Use this tool when a user provides a direct public URL to a resume document and requests resume parsing or candidate information extraction.

Provide the document URL in the url parameter. The RChilli server retrieves and processes the document. For resume text or Base64-encoded file content, use extract_resume_data instead.

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

Input Schema

NameRequiredDescriptionDefault
urlNoDirect, publicly accessible URL to the resume/CV document (pdf, doc, docx, rtf, etc.). The server fetches it directly.

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific result payload. The exact fields depend on which tool produced this result.
metaYesRequest metadata: unique trace ID and server-side processing latency.
successNoAlways ``true`` for a successful result. Check this field first to distinguish success from error envelopes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation that involves an open-world external call. The description adds that the RChilli server directly retrieves and processes the document and that the URL must be publicly accessible, which is useful behavioral context beyond the annotations. It does not cover failure modes, rate limits, or authentication requirements, so it is strong but not exhaustive.

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 short and front-loaded: purpose first, then usage guidance, then parameter handling and the alternative tool. Every sentence contributes useful routing or behavioral information, with no redundant or filler text.

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 a one-parameter tool with full schema coverage, annotations, and an output schema, the description covers what the agent needs: what it does, when to use it, how to supply the URL, and which sibling to choose for text or Base64 input. Return values need not be explained because an output schema exists.

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%, so the url parameter is already documented as a direct, publicly accessible URL to a resume/CV document with supported formats listed. The description restates that the URL should be provided and that the server fetches it, adding only mild reinforcement beyond the schema. The baseline of 3 is appropriate when the schema carries the parameter semantics.

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 names a specific verb and resource: extracting structured candidate information from a resume or CV at a public document URL. It also distinguishes this URL-based path from the sibling tool extract_resume_data, making the tool's identity clear without opening the schema.

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 explicitly states when to use this tool: when the user provides a direct public URL to a resume document and requests parsing or candidate information extraction. It also names the alternative for resume text or Base64-encoded file content, routing the agent correctly between siblings.

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