Teddit

Create a site

create_project

Create a new tracked site (project) and return it with its id. Give the brand name as answers spell it, the domain, other spellings (brandTerms) and the competitors to measure it against; language and location set where the questions are asked from. Next add questions with add_prompts or import_queries, then run start_scan. To change an existing site use update_project.

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

Input Schema

Name	Required	Description
`url`	Yes	The site, e.g. "acme.com".
`name`	Yes	The brand name as it appears in answers.
`industry`	No	The industry in a few words, e.g. "email marketing software".
`language`	No	Answers are asked for in this language. Default English.
`location`	No	Where the buyer is. Default United States.
`brandTerms`	No	Other spellings that still mean this brand.
`competitors`	No	Competitors to measure against: name, and domain when known.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: the call returns the new project with its id, and it establishes the required downstream sequence (prompts, then scan). It does not address duplicate-site handling or what happens if the same domain already exists.

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 sentences, front-loaded with the core action and its return value, followed by the workflow and the sibling redirect. The middle sentence is a dense run-on listing several parameters, but every clause carries actionable information.

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 seven-parameter creation tool with no output schema, the description covers purpose, return value (id), and the follow-on sequence, which is what an agent needs to place this call in a larger flow. Gaps remain around duplicate detection and whether competitors can also be attached later via add_competitor.

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 the schema already defines all seven parameters including brandTerms and the competitors object shape. The description restates intent for name, url, brandTerms, competitors, language and location, but largely echoes the schema's own wording rather than adding new semantics such as format rules or defaults.

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 ('Create a new tracked site (project)'), clarifies the project/site synonym, and notes it returns the created object with its id. It is immediately distinguishable from update_project, which is named explicitly.

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?

Provides an explicit workflow: create the site, then add questions with add_prompts or import_queries, then run start_scan. It also names the alternative for the mutation case ('To change an existing site use update_project'), leaving nothing to inference.

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

All Teddit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?