Skip to main content
Glama

Draft Website Description

analyze_website

Reads a website's public homepage and returns an AI-written business description for drafting or previewing site copy before creating or updating a website.

Instructions

Read the public homepage of the user's website and return an AI-written business description as { description }, without creating or changing any website. Use it to draft or preview the text before create_website or update_website, then pass the result as their description. Consumes one AI generation from the monthly quota unless a precomputed description already exists for that domain, and refunds it if generation fails. Returns 400 when the quota is exhausted or url is not a valid URL, and an error when the page has too little readable text.

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": {
      "url": "<url>"
    },
    "name": "analyze_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAddress of the user's website whose homepage to read, including the scheme, e.g. "https://example.com"
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.6.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / url / description
      Previous value: -"Full website URL to scrape (e.g. \"https://example.com\")"New value: +"Address of the user's website whose homepage to read, including the scheme, e.g. \"https://example.com\""
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another",
      +  "type": "string"
      +}
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedOutput schema / properties / result / additionalProperties
      Added value: +true
    • removedOutput schema / properties / result / description
      Removed value: -"{ description }: the AI-written business description, ready to pass to create_website or update_website."
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "description": {
      +    "description": "AI-written business description to pass to create_website or update_website",
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "description"
      +]
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  2. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / url / description
      Previous value: -"Website URL to analyze"New value: +"Full website URL to scrape (e.g. \"https://example.com\")"
    • changedOutput schema / properties / result / description
      Previous value: -"The AI-generated business description for the analyzed URL."New value: +"{ description }: the AI-written business description, ready to pass to create_website or update_website."
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses quota accounting ('consumes one AI generation from the monthly quota unless a precomputed description already exists for that domain, and refunds it if generation fails'), failure modes (400 on exhausted quota or invalid URL, error on too little readable text), and caching behavior keyed by domain. That is exactly the kind of cost/side-effect context readOnlyHint=false hints at but cannot explain.

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?

Purpose is front-loaded in the first clause, and every subsequent sentence carries quota, error, or handoff information that earns its place. The second sentence is long and packs quota logic plus two error codes together, which slightly hurts scanability.

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?

With an output schema present, the description only needs to name the return field, which it does ({ description }), and it goes further by covering cost, caching, refunds, and error conditions. Nothing an agent needs to decide whether to call this or how to recover from failure is missing.

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 description coverage is 100%, so url and workspaceId are already documented in detail in the schema, and the description adds only the url-validity failure condition. It adds no workspace-scoping guidance of its own, so it sits at the baseline for a fully documented schema.

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?

The description opens with a specific verb and resource -- 'Read the public homepage of the user's website and return an AI-written business description as { description }' -- and immediately delimits scope with 'without creating or changing any website', which separates it from the create/update siblings. An agent can tell exactly what this does and what it does not do without opening the 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?

It explicitly routes usage: 'Use it to draft or preview the text before create_website or update_website, then pass the result as their description', naming the downstream alternatives and the handoff. The exclusion ('without creating or changing any website') makes clear it is not a substitute for the mutation tools.

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