Skip to main content
Glama
Sign In

Replo

by app.replo.api
OverviewDiscussionsAdmin

Find a brand's angles

sightglass_find_angles
Read-onlyIdempotent

A brand's angles: the pitch each ad leans on, for whom; offers sit on top. Each angle has a type (problem/solution, proof, founder story…), a short name for the idea, the newest headline hook, the persona it speaks to (a segment nickname, the buyer's situation in their words, an age range when the ad shows one, and awareness stage from unaware to most-aware), the product, how many ads (and live ads) and landing pages use it, when it was first and last seen, and the offers the same ads carried. Most used first. Use it to answer 'how does this brand sell' or to compare two brands' messaging. Fields the user's Replo plan doesn't include come back null and are named in that item's locked list (estimates = sales, visits and traffic); lockedCount is how many more results a higher plan shows. Say the data is on a higher plan; never estimate it yourself. Returns data only: nothing is shown to the user yet. Once you know the answer, call sightglass_show once with this call's resultId to show it as cards; the show call does not search again.

Input Schema

NameRequiredDescriptionDefault
projectIdNoReplo project id, from list_projects: where the charge or the asset lands. Its workspace's plan applies.
companyRefYesCompany id or slug. Users call companies 'brands'.
workspaceIdNoReplo workspace id, from list_workspaces. Sets which workspace's plan applies; required when the user has more than one workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / projectId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / workspaceId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses significant behavior: results are data-only and nothing renders to the user until sightglass_show is called with resultId (and show does not re-search). It also explains plan-gated fields — locked values return null, `estimates` covers sales/visits/traffic, `lockedCount` quantifies what a higher plan reveals — and explicitly forbids the agent from estimating them.

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?

It is one very dense block, but it is front-loaded with the definition, then the use cases, then the plan-lock caveat, then the mandatory show step — a sensible escalation. The run-on enumeration of angle fields is heavy but each element (locked, lockedCount, show/resultId) earns its 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 fully carries the burden: it enumerates the returned fields, states ordering, explains null/locked semantics, and closes the loop on the two-step display workflow. An agent can call this and correctly follow up without opening anything else.

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 carries parameter meaning and a baseline of 3 applies. The description reinforces that 'company' means 'brand' and that a workspace's plan determines which fields lock, but adds no syntax or selection rules for the three ids beyond what the schema states.

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 defines the resource in depth — what an 'angle' is, every field it carries (type, persona, ad/live-ad counts, offers), and the ordering rule ('Most used first'). The verb is clear ('find'/'how does this brand sell'), but it never distinguishes this tool from its close siblings like sightglass_find_top_angles or sightglass_find_personas, which an agent could easily confuse it with.

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?

Explicit use cases are given: answer 'how does this brand sell' or compare two brands' messaging, plus a clear follow-up instruction ('call sightglass_show once with this call's resultId'). There is, however, no when-not-to-use guidance or pointer to the alternative angle/persona/offer tools, so sibling routing is left to inference.

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

All Replo toolsInspect
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