Skip to main content
Glama

Import website

import_website
Destructive

Start a website import for activity drafts.

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": {
      "urls": "<urls>"
    },
    "name": "import_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

Beyond the annotations, 'Start' suggests that the tool initiates rather than completes the import, and 'activity drafts' clarifies the immediate result. However, it does not explain the destructiveHint risk, whether existing website or activity data can be replaced, or how the import progresses and is monitored.

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

Conciseness5/5

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

The single sentence is front-loaded with the action and contains no unnecessary wording. Its brevity is effective, while the missing operational detail is assessed under the other dimensions.

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?

Although the input schema is small, this is a non-read-only, destructive import operation with no output schema, so the minimal description leaves important invocation context unresolved. In particular, it lacks source-URL expectations, destructive-effect clarification, and guidance on tracking the started import.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents business_id, including its source and single-business optionality, but the required urls parameter has no description. The tool description does not compensate by explaining that these are source website URLs, what URL forms are accepted, or how multiple URLs are handled.

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 gives a specific action and outcome: starting a website import that produces activity drafts. It does not explicitly differentiate the tool from siblings such as get_website, update_website, or create_activity.

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 'for activity drafts' implies when the tool is useful, namely importing website material as drafts rather than directly creating an activity. There is no explicit guidance about prerequisites, when not to import, or how get_import_status should be used after starting the import.

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