Skip to main content
Glama

AIApply

Track AIApply applications

list_applications
Read-onlyIdempotent

Use this when the connected user wants recent AIApply application and preparation status. Return role, company, status, match score, timestamp, and canonical listing link without exposing resumes or contact details. Needs an AIApply account: if the user has not signed in, calling it asks them to sign in or create one.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of recent applications, from 1 to 20.

Output Schema

NameRequiredDescriptionDefault
viewYes
countYes
applicationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds context annotations cannot: it withholds resumes and contact details (a privacy guarantee), states an AIApply account is required, and warns that calling it triggers a sign-in/create-account prompt when unauthenticated — a real behavioral side effect an agent must anticipate.

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 tight sentences, each carrying distinct load: trigger condition first, output/privacy contract second, authentication prerequisite third. No filler and no repetition of the title.

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?

An output schema exists, so the field enumeration is partly redundant, but it usefully pairs the returned fields with the privacy exclusion. Combined with the auth prerequisite and the annotations, an agent has everything needed to call this correctly; only the absence of any recency-ordering detail is a minor gap.

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?

There is a single parameter, and the schema already documents it fully (default 10, range 1 to 20) at 100% coverage. The description says nothing about the limit or how recency is determined, so it adds no meaning beyond the schema; baseline 3 applies.

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 the resource precisely (recent AIApply applications plus preparation status) and enumerates the returned fields (role, company, status, match score, timestamp, canonical listing link), so an agent knows exactly what this tool surfaces. It never names a sibling such as list_review_jobs or list_unread_mail, so differentiation rests on the resource noun alone.

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?

"Use this when the connected user wants recent AIApply application and preparation status" gives an explicit trigger condition tied to user intent, which is more than most definitions offer. There are no when-not conditions or named alternatives, but the trigger is concrete enough to route correctly.

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