Skip to main content
Glama
Unilytics MCP Server

Unilytics MCP Server

Official

kb_add_urls

Add webpage URLs to a knowledge base so each page is scraped and ingested as a separate document; returns a job ID for background processing you can track with kb_get_status.

Instructions

Add one or more webpage URLs to a KB — each is scraped + ingested as its own document. Returns a job id; ingestion runs in the background and kb_get_status reports each document's progress. The same metadata hash is applied to every document.

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": {
      "project_id": "<project_id>",
      "collection_id": "<collection_id>",
      "urls": "<urls>"
    },
    "name": "kb_add_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes
metadataNo
project_idYes
collection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • removedInput schema / properties / config
      Removed value: -{
      -  "default": null,
      -  "title": "config",
      -  "type": "string"
      -}
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly=false, destructive=false, openWorld=true, idempotent=false), and the description adds genuinely new behavior: scraping, one document per URL, an async background job returning a job id, and the shared-metadata rule. It does not mention deduplication of repeated URLs or error handling for failed scrapes, but the core execution model is disclosed well beyond the annotations.

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?

Three short sentences, front-loaded with what the tool does, then the return value, then the metadata rule. Every sentence carries information; no filler or restated name.

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 four-parameter mutation with no output schema, the description covers the essential flow: input shape, asynchronous execution, how to observe results via kb_get_status, and how metadata propagates. The remaining gaps are the two identifier parameters and failure/retry behavior, which are secondary to calling the tool correctly.

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 0%, so the schema provides no help, and the description only partially compensates: it explains that 'urls' is one-or-more webpages and that 'metadata' is a single hash applied to every document. project_id and collection_id — two of the three required parameters, plus the nested metadata object's keys — receive no explanation anywhere.

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 verb and resource ('Add one or more webpage URLs to a KB') and clarifies the resulting unit of work ('each is scraped + ingested as its own document'), which separates it from a plain text-write or file-upload path. It does not explicitly name kb_add_file or kb_write_text as the alternative, so the sibling boundary is implied rather than stated.

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?

It points the agent to kb_get_status for progress, which is useful follow-up guidance, but it never says when to choose this over kb_add_file, kb_write_text, or kb_create_direct_upload. Usage is implied by the 'webpage URLs' framing rather than stated as a selection rule.

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

Deploy Server

Other Tools