Skip to main content
Glama

AIApply

Preview a prepared AIApply application

preview_application
Read-onlyIdempotent

Use this when the connected user asks what AIApply prepared for one specific application, identified by the job_id returned from list_applications or list_review_jobs. Read the cover letter AIApply wrote, unless it was withheld. This never submits, approves, edits, or withdraws anything, and it returns neither the resume file nor the form answers. Needs an AIApply account: if the user has not signed in, calling it asks them to sign in or create one.

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": {
      "job_id": "<job_id>"
    },
    "name": "preview_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id from list_applications or list_review_jobs.

Output Schema

NameRequiredDescriptionDefault
jobNoNull when no such application belongs to the account.
viewYes
messageYes
answer_countYesHow many form answers AIApply prepared. The answers themselves stay in AIApply, since the questions are employer-written and carry no category metadata to tell a protected trait from an ordinary question.
cover_letterNoNull when the application has no cover letter, and also when one was withheld; cover_letter_withheld tells the two apart.
resume_attachedYes
cover_letter_withheldYesTrue when a cover letter exists but was withheld for carrying contact details, credentials, health information or embedded instructions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, yet the description still adds real value: it names the operations this never performs (submit, approve, edit, withdraw), discloses which return content is excluded (resume file, form answers), warns that the cover letter may be withheld, and explains the unauthenticated sign-in prompt.

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?

Three sentences, front-loaded with the trigger condition, then the return scope, then exclusions and the auth caveat. Every clause carries distinct information with no restatement of the title or name.

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?

An output schema exists so return values need not be described, and the description completes the picture with auth requirements and explicit content exclusions. Nothing an agent needs in order to decide to call this tool or to interpret its limits 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 coverage is 100% and the single parameter is fully documented in the schema, including the same provenance note that appears in the description. The description adds no new meaning about format, validation, or sourcing beyond what the schema already provides.

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 states a specific verb (preview/read) applied to a specific resource (one prepared application), scoped to a single job_id. It immediately distinguishes itself from list_applications and list_review_jobs by framing this as the per-application view of what AIApply wrote.

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 gives an explicit trigger condition ('when the connected user asks what AIApply prepared for one specific application') and names the two sibling tools that supply the job_id input. It also states what the tool does not do, so the agent knows not to reach for it for submission or editing.

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