Skip to main content
Glama

Get Monitored Website

get_website
Read-onlyIdempotent

Retrieve one monitored website by ID to inspect its full keyword list, statuses (PENDING, ACTIVE, DISABLED, SUSPENDED), and ignored keywords; use it to re-check keyword statuses.

Instructions

Get one monitored website by ID with its full keyword list and statuses (PENDING, ACTIVE, DISABLED, SUSPENDED), and its ignoredKeywords: the words and phrases whose mentions are hidden. Use it to re-check keyword statuses after add_keywords or enable_keyword; use list_websites instead when you do not have the ID yet or want every site. websiteId comes from list_websites or create_website. Returns 404 when the website does not exist or belongs to another account.

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": {
      "websiteId": "<websiteId>"
    },
    "name": "get_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteIdYesWebsite ID from list_websites or create_website
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. Changed11 schema fields changedv1.6.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / websiteId / description
      Previous value: -"Monitored website ID (UUID) from list_websites"New value: +"Website ID from list_websites or create_website"
    • addedInput schema / properties / websiteId / format
      Added value: +"uuid"
    • 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: -"The monitored website with its keyword list, each keyword carrying id, value, and status."
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "accountGroupId": {
      +    "description": "Workspace the website belongs to",
      +    "type": "string"
      +  },
      +  "createdAt": {
      +    "description": "When the website was added, ISO 8601",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "description": {
      +    "description": "Context every new mention is scored against; null means new mentions go unscored",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "domain": {
      +    "description": "Domain taken from url; identifies the site in this account",
      +    "type": "string"
      +  },
      +  "id": {
      +    "description": "Website ID for the other tools",
      +    "type": "string"
      +  },
      +  "ignoredKeywords": {
      +    "description": "Lowercased words and phrases; mentions containing one are hidden",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "keywords": {
      +    "description": "Every keyword on the website, in any status",
      +    "items": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "createdAt": {
      +          "description": "When the keyword was added, ISO 8601",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "id": {
      +          "description": "Keyword ID for edit_keyword, enable_keyword, disable_keyword and delete_keyword",
      +          "type": "string"
      +        },
      +        "status": {
      +          "description": "PENDING (saved, not monitored until the plan covers it), ACTIVE, DISABLED or SUSPENDED",
      +          "type": "string"
      +        },
      +        "updatedAt": {
      +          "description": "When the keyword last changed, ISO 8601",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "value": {
      +          "description": "Lowercased keyword text, the value list_mentions filters on",
      +          "type": "string"
      +        },
      +        "websiteId": {
      +          "description": "Website this keyword belongs to",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "websiteId",
      +        "value",
      +        "status",
      +        "createdAt",
      +        "updatedAt"
      +      ],
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "name": {
      +    "description": "Display name; null when none was set",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "updatedAt": {
      +    "description": "When the website last changed, ISO 8601",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "url": {
      +    "description": "Website address as saved",
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "id",
      +  "accountGroupId",
      +  "domain",
      +  "url",
      +  "name",
      +  "description",
      +  "ignoredKeywords",
      +  "createdAt",
      +  "updatedAt",
      +  "keywords"
      +]
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  2. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / websiteId / description
      Previous value: -"Monitored website ID (UUID)"New value: +"Monitored website ID (UUID) from list_websites"
    • changedOutput schema / properties / result / description
      Previous value: -"The monitored website with its keywords and their statuses."New value: +"The monitored website with its keyword list, each keyword carrying id, value, and status."
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior: a 404 when the website does not exist or belongs to another account, plus the PENDING/ACTIVE/DISABLED/SUSPENDED status vocabulary and the meaning of ignoredKeywords. It stops short of noting anything about payload size for large keyword lists, which keeps it from a 5.

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?

Front-loads the return contents, then usage, then the error case, in a logical order with no filler. It is dense but a bit run-on, packing return shape, routing advice, provenance and error behavior into one block.

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?

A read-only single-record fetch with an output schema, full annotation coverage and complete parameter documentation needs only routing and error guidance, both of which are present. Nothing an agent needs in order to call this correctly 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 both parameters are already documented, and the description's provenance note ("websiteId comes from list_websites or create_website") merely repeats the schema's own wording. workspaceId, the parameter that carries the subtle cross-workspace id constraint, is never mentioned in the description. Baseline 3 is appropriate since the schema does the work.

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?

States a specific verb and resource ("Get one monitored website by ID") and enumerates the payload contents: full keyword list with statuses and ignoredKeywords. It explicitly separates itself from list_websites, so an agent can pick the right tool without opening either 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?

Gives an explicit when-to-use (re-check keyword statuses after add_keywords or enable_keyword) and an explicit when-not-to-use with the named alternative ("use list_websites instead when you do not have the ID yet or want every site"). Both the positive and negative conditions are covered.

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