Skip to main content
Glama

Report a job site signed out or limited

freeapply_report_site_problem
DestructiveIdempotent

Marks a chosen job site as signed out or daily-limit reached so FreeApply pauses applications there until the user resolves it. Use when a site shows a sign-in page or its own limit.

Instructions

Marks a job site the user chose in Settings (e.g. LinkedIn, Indeed) unusable for now: it signed the user out or showed its own daily limit (an employer's own careers site: freeapply_find_site_account). Use: as soon as a chosen site shows a sign-in page or a daily limit; then keep applying on the ready sites or company career sites. Never type a password. Behavior: signed_out: unavailable until the user signs in again and confirms it in the dashboard; limit_reached: paused until midnight. Meanwhile freeapply_claim_job refuses new jobs from it. Reporting again changes nothing; only the user can mark a site ready. Returns: {site, status, sites} (each chosen site with ready). Errors: a site the user didn't choose.

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": {
      "site": "<site>",
      "status": "<status>"
    },
    "name": "freeapply_report_site_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesJob site id, as freeapply_get_status lists it in sites.
statusYessigned_out: a sign-in page, or the site says you're signed out. limit_reached: the site's own daily limit, e.g. "You reached today's Easy Apply limit".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.6
    • changedInput schema / properties / site / description
      Previous value: -"Job site id, as freeapply_status lists it in sites."New value: +"Job site id, as freeapply_get_status lists it in sites."
  2. Changed2 schema fields changedv1.0.4
    • changedInput schema / properties / site / description
      Previous value: -"The job site, as listed in freeapply_status sites."New value: +"Job site id, as freeapply_status lists it in sites."
    • changedInput schema / properties / status / description
      Previous value: -"What the site showed."New value: +"signed_out: a sign-in page, or the site says you're signed out. limit_reached: the site's own daily limit, e.g. \"You reached today's Easy Apply limit\"."
  3. Addedv1.0.2

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it explains the per-status consequences (unavailable until the user signs in and confirms; paused until midnight), the downstream effect on freeapply_claim_job, and that re-reporting is a no-op and only the user can restore readiness. That gives the agent the lifecycle and side effects of a destructiveHint=true mutation, which the annotations alone do not convey.

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?

Front-loaded with the action, then labeled Use/Behavior/Returns/Errors sections, with no filler sentences. The telegraphic, colon-heavy style is dense but each line carries information an agent needs.

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?

Fills the gap left by the absent output schema by documenting the return shape {site, status, sites} and names the error case (a site the user didn't choose). Combined with the state-transition details, an agent has everything needed to call it correctly and interpret the result.

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 both parameters are fully described in the schema, including enum meanings and example phrasing for limit_reached. The description adds only illustrative site examples and the note that only user-chosen sites are valid, so baseline 3 is right.

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?

States a precise verb+resource (marks a chosen job site unusable) with the concrete trigger conditions (signed out or daily limit). It also distinguishes the employer-careers case by routing to freeapply_find_site_account, so an agent can separate this from sibling tools without opening a 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?

Gives an explicit trigger ('as soon as a chosen site shows a sign-in page or a daily limit'), the required follow-up behavior ('keep applying on the ready sites or company career sites'), and a hard exclusion ('Never type a password'). Alternatives are named rather than implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.