Skip to main content
Glama
Ashby MCP Server

Ashby MCP Server

ashby_open

Open a page in your signed-in Cloud Browser to manage Ashby jobs, candidates, interviews, and offers.

Instructions

Open a Ashby page in your signed-in Cloud Browser (default https://app.ashbyhq.com) to work with jobs, candidates, interviews and offers.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://app.ashbyhq.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one real trait: the target is a signed-in Cloud Browser session, so authenticated state is assumed, plus the default URL. It does not say whether opening replaces the current page/session state, what is returned (no output schema), or how navigation failures surface, which leaves meaningful behavioral gaps.

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?

A single front-loaded sentence that names the action, the environment and the default target with no filler. Minor grammar slip ("a Ashby") and the trailing beneficiary list is slightly padded, but overall efficient.

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?

For a one-parameter navigation tool with no output schema, the definition supplies the environment, the domain and the default URL, which is enough to invoke it correctly. What the agent should do after opening a page is only implied, which keeps it from a 5.

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?

Only one optional parameter, and the schema already documents it at 100% coverage including the same default URL. The description restates the default but adds no format or path semantics beyond the schema, so the 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?

States a specific verb ("Open") and a specific resource ("a Ashby page in your signed-in Cloud Browser"), scoped to the Ashby domain with a concrete default URL. It hints at the domain of work (jobs, candidates, interviews, offers) but never names how it differs from ashby_read or ashby_status, so sibling differentiation is left implicit.

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 "to work with jobs, candidates, interviews and offers" implies this is the entry point for a session, but there is no explicit when-to-use rule and no mention of ashby_read as the follow-up for fetching page content. Usage is inferred rather than stated.

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