Skip to main content
Glama

Yellowhead Digital agent door

Start a free Diagnostic

start_diagnostic

Starts a Diagnostic of a website for the signed-in person, in two calls. The first call returns a preview and starts nothing: the website, the business name, the ten 1-to-10 self-ratings (which were answered, carried over or entered as 5 for "not sure"), the monthly tools budget, where the run is filed, which of the account's included monthly Diagnostics it uses, and a confirmation_token. A second call with that token starts it; any change needs a new preview. It uses only the account's included Diagnostics: when none are left the result is quota_exhausted with the reset date and the plans page, and nothing is charged. A run takes 5 to 10 minutes and a completion email also arrives; get_run_status reports progress. earlier_report_id fills in the website, name, ratings and budget from an earlier report, for a re-check; if that run did not complete and the same person started it, starting it again once for the same website and name does not use another Diagnostic (the preview says whether it applies). On an account with workspaces (clients, prospects or brands), client_id or file_as says where the run is filed, and needs_client lists the candidates when that is not clear. For an owner or admin of an Agency-plan team account, file_as prospect on a website not yet in Prospects creates a new prospect workspace for it (named by prospect_name, else the business name); the preview says so and nothing is created before the confirmation. The same person may ask for a new client workspace for a website no workspace holds: file_as client with client_name (the new workspace's name); without client_name a miss lists the client workspaces instead. Available on connections made through an AI assistant's sign-in.

Input Schema

NameRequiredDescriptionDefault
urlNoThe website to check, as the person gave it (a domain or an http/https address). Tracking parameters are removed, and the address that remains must be at most 2048 characters. Optional with earlier_report_id.
budgetNoRoughly what the business spends a month on marketing tools and software, in whole US dollars. Null when unknown: it is then entered as 0, the intake form's own default. Left out, it is also entered as 0, except with earlier_report_id, where the earlier report's budget is carried over.
file_asNoWhat the person asked for when no client_id is sent: prospect (filed in Prospects; for an owner or admin of an Agency-plan team account, a website not yet in Prospects gets a new prospect workspace), client (with client_name, the same person may have a new client workspace created for a website no workspace holds), or own (the account's own website or one of its brands: filed in the brand's workspace when the site matches one, else in no workspace; recorded as the account's own business). A run in no workspace without own is recorded as research on another business; the preview says which.
client_idNoThe client, prospect or brand workspace to file the run in. It must be a workspace of this account.
client_nameNoAsks for a new client workspace with this name, for a website no workspace of the account holds. Sent only with file_as client and without client_id, and only when the person asked for a new client workspace; for an owner or admin of an Agency-plan team account. Invisible and control characters are removed; it needs a letter or digit.
business_nameNoThe name of the business that operates the website, as the person gave it. Optional with earlier_report_id.
prospect_nameNoThe name of a new prospect workspace, sent only with file_as prospect and without client_id. Left out, the business name is used. Invisible and control characters are removed; it needs a letter or digit.
side_a_scoresNoThe person's own 1-to-10 rating of each area, keyed attribution, tech_stack, conversion, compliance (shown to people as Trust & Security), brand, marketing, advertising, competitors, product and discoverability. An area left out is "not sure" and is entered as 5, the intake form's own default.
earlier_report_idNoAn earlier Diagnostic of this account whose website, business name, ratings and budget fill in anything not sent.
confirmation_tokenNoThe token from this tool's preview. Present only on the second call, which starts the run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive, so the safety profile is largely covered. The description still adds substantial value beyond that: nothing is created or charged on the first call, quota_exhausted returns a reset date and plans page, a run takes 5-10 minutes with a completion email, and a repeat start after an incomplete run does not consume another Diagnostic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one dense ~350-word paragraph with no breaks, packing quota behavior, timing, workspace filing, Agency-plan prospect creation, client workspace creation, and connection requirements into undifferentiated prose. The two-call protocol is correctly front-loaded, but several clauses are hard to parse on a single read and would benefit from structure.

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 10-parameter, no-output-schema, multi-phase tool it is unusually complete: it describes exactly what the preview returns, what the token does, what is and isn't created before confirmation, and how progress is checked. The main remaining gap is the unresolved relationship with the sibling run_diagnostic.

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%, so every parameter is already documented in the schema, which sets the baseline at 3. The description does add cross-parameter meaning the schema cannot express - earlier_report_id backfilling website, name, ratings and budget, and ratings defaulting to 5 for "not sure" - but the file_as/client_name/prospect_name rules largely restate schema text.

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 a specific verb and resource ("Starts a Diagnostic of a website for the signed-in person") and immediately frames the two-call preview/confirm protocol, so the agent knows what the tool does. It does not, however, distinguish itself from the sibling run_diagnostic, leaving ambiguity about which entry point to pick.

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?

Rich conditional guidance: when earlier_report_id should be used (a re-check), when file_as prospect creates a workspace, when client_name is allowed, and what happens when quota is exhausted. What is missing is any explicit statement of when to prefer this over run_diagnostic or how it relates to list_diagnostics/get_run_status beyond the passing mention of progress reporting.

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