Skip to main content
Glama

AceRound AI Interview Copilot

get_job_apply_profile

Read-only

Show the user's Auto Apply profile: standard fields (key, value, source) and answers learned from past applications (normalized question key, value, company). Filter learned answers by keyword when there are many. (Requires the user's sign-in with scope job_applications:read.)

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

Input Schema

NameRequiredDescriptionDefault
keywordNoOnly list learned answers whose question or value contains this (optional)

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 readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: it discloses the required auth scope (job_applications:read) and sketches the shape of the returned data (standard fields versus learned answers, with their respective attributes). It does not mention pagination limits or ordering, but given the annotation coverage this is a solid contribution.

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?

The description is compact and front-loaded, leading with the resource and then enumerating its two content categories. The auth requirement is placed in a trailing parenthetical, which is a sensible spot for a secondary constraint. The 'when there are many' clause is slightly loose prose but does not waste much space.

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?

For a single-parameter read tool with no output schema, the description is complete: it explains what is returned (including field-level attributes), notes the filtering behavior, and states the required OAuth scope. An agent could select and invoke this correctly without opening the schema. Nothing material is missing given the read-only annotation set.

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% and the single keyword parameter is already documented as a containment match on question or value, so the schema carries the weight. The description's 'Filter learned answers by keyword when there are many' reinforces the practical use of the parameter but adds no syntax or scoping detail beyond what the schema states, notably that filtering deliberately does not apply to standard fields. Baseline 3 is appropriate here.

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 names a specific verb and resource ('Show the user's Auto Apply profile') and then breaks the resource down into its two constituent parts: standard fields (key, value, source) and learned answers (normalized question key, value, company). That is far more specific than a tautology. It doesn't explicitly contrast itself with the mutating siblings like update_job_apply_profile or delete_learned_profile_answer, but the read-only framing ('Show') effectively signals the distinction.

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?

The only usage guidance is the parenthetical instruction to 'Filter learned answers by keyword when there are many', which is really a hint about the keyword parameter rather than a statement of when to call this tool. There is no explicit when-not guidance and no named alternative (e.g., pointing to extract_job_apply_profile_from_resume to populate an empty profile). Usage is therefore implied rather than stated.

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