Skip to main content
Glama

Add Your Website

create_website

Add a website to RedReplier so its public mentions across Reddit, Hacker News, X, Bluesky, and Facebook are found and scored against a product description you provide or let RedReplier generate.

Instructions

Add the user's own website to their RedReplier account so RedReplier can find public posts on Reddit, Hacker News, X, Bluesky, and Facebook that mention its keywords. The domain must be new to this account: a duplicate returns 400, and re-adding a domain removed with delete_website revives that record. description is the context every mention is scored against. Omit it and RedReplier reads the website's public homepage to write one, spending one AI generation from the plan quota; if that read fails or the quota is exhausted the site is created with description null and its mentions go unscored (reason "Scoring skipped: website description missing"), so check the response and set one with update_website or analyze_website. Pass your own description to skip that step. Returns the new website with its id, domain, description, ignoredKeywords and keywords. Initial keywords are saved as PENDING and stay PENDING until add_keywords or enable_keyword activates them within the plan. AI-suggested keywords are added in the background and show up on the website later. Returns 400 when the plan has no website slots left.

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": "create_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAddress of the user's website including the scheme, e.g. "https://example.com". Its domain identifies the site
nameNoDisplay name for the website in RedReplier, e.g. "Acme CRM". Omit to store no name (null); set one later with update_website
keywordsNoWords or phrases whose mentions to look for. Saved as PENDING; activate them with add_keywords or enable_keyword. Omit to start with none
descriptionNoProduct summary the AI scores every mention against. Omit to have RedReplier write one from the homepage (one AI generation); an empty string stores none and leaves new mentions unscored. Draft one with analyze_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. Changed14 schema fields changedv1.6.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / description / description
      Previous value: -"Product summary the AI scores every mention against; without it new mentions are not scored. Draft one with analyze_website"New value: +"Product summary the AI scores every mention against. Omit to have RedReplier write one from the homepage (one AI generation); an empty string stores none and leaves new mentions unscored. Draft one with analyze_website"
    • changedInput schema / properties / keywords / description
      Previous value: -"Initial keywords, stored as PENDING; list_websites promotes those that fit the plan for free"New value: +"Words or phrases whose mentions to look for. Saved as PENDING; activate them with add_keywords or enable_keyword. Omit to start with none"
    • addedInput schema / properties / keywords / maxItems
      Added value: +100
    • changedInput schema / properties / name / description
      Previous value: -"Display name for the website"New value: +"Display name for the website in RedReplier, e.g. \"Acme CRM\". Omit to store no name (null); set one later with update_website"
    • changedInput schema / properties / url / description
      Previous value: -"Full website URL (e.g. \"https://example.com\")"New value: +"Address of the user's website including the scheme, e.g. \"https://example.com\". Its domain identifies the site"
    • 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 created website with its id, domain, description, and keywords (initial ones PENDING)."
    • 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. Changed3 schema fields changedv0.1.1
    • changedInput schema / properties / description / description
      Previous value: -"Manual description (skips scraping/AI). Used as context when scoring mention relevance"New value: +"Product summary the AI scores every mention against; without it new mentions are not scored. Draft one with analyze_website"
    • changedInput schema / properties / keywords / description
      Previous value: -"Initial keywords to monitor (added as PENDING)"New value: +"Initial keywords, stored as PENDING; list_websites promotes those that fit the plan for free"
    • changedOutput schema / properties / result / description
      Previous value: -"The created website record with its description and initial keywords with their statuses."New value: +"The created website with its id, domain, description, and keywords (initial ones PENDING)."
  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?

Goes well beyond the annotations (readOnly=false, destructive=false, idempotent=false, openWorld=true) by disclosing the AI-generation quota cost when description is omitted, the exactly-what-happens failure mode (site created with description null and mentions unscored, with the concrete reason string), and that keywords land in PENDING state with background AI suggestions. These are non-obvious side effects an agent cannot infer from the schema.

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 purpose and domain-uniqueness rule, and nearly every sentence carries a distinct fact (quota cost, null-description failure path, PENDING state, return shape). It is a dense single block with no headers or line breaks, which slightly hurts scannability for a definition this information-rich.

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?

For a 5-parameter creation tool with an output schema, the definition covers prerequisites (plan slots, domain uniqueness), cost implications, failure modes, and follow-up actions. Even though the output schema defines the return value, it still summarizes the returned fields so an agent knows to check description after the call.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above that by attaching consequences to the description parameter (quota spend, unscored mentions, remediation path) and to keywords (PENDING until add_keywords/enable_keyword) and url (domain identifies the site, must be new). It adds meaning rather than restating field descriptions.

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?

Opens with a specific verb and resource ("Add the user's own website to their RedReplier account") and immediately scopes what the site is used for (finding public posts mentioning its keywords across named platforms). This clearly separates it from update_website, get_website, and analyze_website, which operate on already-registered sites.

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?

Gives strong operational context: duplicates return 400, re-adding a domain deleted via delete_website revives the old record, and exhausting plan website slots yields 400. It also routes remediation to update_website/analyze_website. It stops short of an explicit "if the site already exists, use update_website instead" exclusion, but the duplicate/revive rules cover most of that ground.

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