Viral Outliers

Save Posts to a Project

add_project_posts

Saves posts into one of your projects. Pass postIds (from search_outliers, get_trending_outliers or get_project) and/or urls (public TikTok, Instagram or YouTube post links); up to 25 per call. A link resolves only when we already have the post (crawl_profile its creator first if not); anything unresolved comes back in notFound with the reason. Posts already in the project are reported in alreadyPresent, not duplicated. Free. Cost: free.

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": {
      "projectId": "<projectId>"
    },
    "name": "add_project_posts"
  }
}

Input Schema

Name	Required	Description
`urls`	No	Public post links to save (postIds + urls <= 25 per call)
`postIds`	No	Internal post ids (from search results or get_project)
`projectId`	Yes	Project id from list_projects or create_project

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing partial-success behavior (unresolved links returned in notFound with a reason) and dedupe behavior (alreadyPresent, no duplication), plus the cost. The only weakness is that no auth or project-ownership requirement is mentioned, which matters for a write tool with readOnlyHint=false.

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-loaded with the action, then inputs, then failure semantics — a sensible order with no filler sentences. The trailing 'Free. Cost: free.' is a redundant restatement that earns no place.

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?

With no output schema, the description takes on the burden of explaining the meaningful response fields (notFound, alreadyPresent) and does so. For a 3-parameter write tool, everything an agent needs to call it correctly and interpret the result is present.

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 already 100%, so the baseline is 3; the description adds real meaning by naming the supported URL platforms (public TikTok, Instagram, YouTube), the source tools for postIds, and the combined 25-item constraint that the schema only states per-field.

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 ('Saves posts into one of your projects') and immediately scopes the two accepted input forms. It is clearly distinguishable from the sibling remove_project_posts and from read-side tools like get_project.

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?

Explains where postIds come from (search_outliers, get_trending_outliers, get_project), when urls will fail (post not yet crawled) and what to do instead (crawl_profile the creator first). It also names the 25-per-call cap, so an agent can decide before calling whether to batch.

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

All Viral Outliers 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?