Skip to main content
Glama

Niche — Editorial Intelligence

by com.nicheangle

Brand kit guided setup

niche_brand_kit_guided_setup
Read-only

Return a structured question chain the agent walks the user through to populate the BrandKit, VoiceProfile, and (optionally) BrandProfile. Each entry carries an intent describing what the answer is for (so the agent paraphrases in its own voice based on the conversation it's already having) plus a prompt_hint fallback for agents that relay tools verbatim.

Use this when the agent is helping a new user set up Niche and wants a predictable, brand-aware Q&A sequence instead of improvising. Tiered by impact:

  • Tier 0 (primary): URL ingest, fills 70-90% in one ask.

  • Tier 1 (gap_fill): only the fields URL ingest didn't fill.

  • Tier 2 (discipline): opt-in guardrails (topics off, banned terms, competitor stance).

  • Tier 3 (no_url): full fallback for users without a site.

Per-question applies_to_field tells the agent where the answer writes (via niche_brand_kit_update or niche_brand_profile_set). is_already_set is computed from the user's current BrandKit and BrandProfile state so the agent skips questions already answered.

Returns the full chain in one call; the agent inspects state, decides flow, and asks in any order (or skips entirely if the user volunteered the answer earlier in the conversation).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brand_idNoOptional. If set, also reads the persisted BrandProfile for that brand_id so questions whose answers live in the profile (banned_terms, framing.allowed, etc.) get their is_already_set computed against profile state too.
include_filledNoIf true, return all questions including those already answered. Default false: the agent only sees the gaps.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint true), the description reveals the tool returns a full chain in one call, includes per-question metadata (intent, prompt_hint, applies_to_field, is_already_set), and computes state based on the user's current BrandKit/BrandProfile. It also clarifies the optional brand_id reads profile state, giving a complete behavioral picture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy but well-structured with tiers and per-question details, every sentence adds necessary context about how to use the chain. Front-loaded with the main purpose and then use cases, making it easy to scan.

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?

Given no output schema, the description thoroughly explains the return structure (intent, prompt_hint, applies_to_field, is_already_set) and the agent's possible actions (inspect state, decide flow, ask any order, skip). It covers all necessary context for correct tool invocation.

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?

The input schema already provides descriptions for both brand_id and include_filled, including default behavior and purpose. The main description doesn't add significant extra parameter semantics beyond what the schema covers, so baseline 3 applies.

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?

The description opens with a specific verb 'Return a structured question chain' and identifies the resource (setup for BrandKit, VoiceProfile, BrandProfile). It clearly distinguishes from sibling write tools like niche_brand_kit_update by focusing on the guidance chain, not the actual update.

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?

Explicitly states 'Use this when the agent is helping a new user set up Niche and wants a predictable, brand-aware Q&A sequence instead of improvising.' It further describes tiered scenarios and notes the agent can skip or reorder questions, providing clear contextual guidance versus alternatives.

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

All Niche — Editorial Intelligence toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Tools are mostly distinct across the pipeline—discovery, brand setup, drafting, rendering, publishing, session management—and descriptions are detailed. Minor overlap exists between niche_signal_scan and niche_intelligence_query (both discovery) and between niche_add_output and niche_draft_create (both generate outputs), but the descriptions clearly differentiate them. Overall, an agent can reliably select the right tool.

Naming Consistency3/5

All tools share the `niche_` prefix and snake_case, but the verb/noun order is inconsistent: some are verb-first (add_output, render_image_card, list_sessions) while many are noun-first (angle_propose, brand_kit_ingest, draft_create, session_cancel). This mixed convention requires the agent to learn each name individually rather than predict the pattern.

Tool Count3/5

25 tools is on the heavy side but appropriate for the platform's scope—full editorial intelligence from discovery to publish. No redundant tools, and each covers a distinct aspect, but the count is high enough that it feels dense and may require orientation (which niche_whoami addresses).

Completeness4/5

The toolset covers the full workflow: discovery, angle proposal, drafting, revision, publishing, rendering, asset attachment, brand setup, and session management. Minor gaps exist, such as no direct read tool for the current BrandKit (only via ingest status) and no hard-delete tool (session_cancel mentions the REST endpoint instead), but these are edge cases and agents can work around them.

Resources