Skip to main content
Glama
Ashby MCP Server

Ashby MCP Server

ashby_click

Clicks a numbered element on the current Ashby page to interact with jobs, candidates, applications, interviews, or offers. Use the element number from the last page read.

Instructions

Click a numbered element on the current Ashby page.

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": {
      "element": "<element>"
    },
    "name": "ashby_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for a UI action that can navigate, submit, or mutate state. It conveys only that the element is on the 'current page' and comes from the last read; it says nothing about whether the page changes, whether the click is irreversible, whether the element index becomes stale after the click, or what the tool returns.

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?

One front-loaded sentence with zero filler. It is appropriately tight, though the brevity is partly under-specification rather than pure economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description must cover behavior on its own for a state-changing browser interaction, and it does not. An agent cannot tell from this definition whether a subsequent ashby_read is required, whether the click may navigate away, or what changed afterwards.

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 documented as 'Element number from the last read', so the schema does the heavy lifting. The description reinforces the 'current page' scoping of the index but adds no format, range, or staleness detail beyond the schema.

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?

States a specific verb ('Click') and a specific target ('a numbered element on the current Ashby page'), so the action is unambiguous. It implicitly contrasts with ashby_read/ashby_type via the word 'click', but never explicitly distinguishes itself from the other interaction-style siblings.

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 phrase 'numbered element' plus the schema note 'Element number from the last read' implies a required workflow (read first, then click), which is useful implied guidance. However, there is no explicit when-to-use guidance, no statement of when to prefer ashby_type or ashby_read over clicking, and no mention of what the click must target (link, button, etc.).

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