Metadata MCP Connector

Get Intent Topics

get_intent_topics

Read-only

Get available intent topics for BOMBOORA audience creation.

                    IMPORTANT:
                    Call this tool first before suggesting or creating any Bombora audience.
                    If the response returns NO topics (empty list), Bombora is NOT available for this account —
                    do NOT suggest Bombora audiences. Instead, recommend creating a firmographic audience
                    (create_firmographic_audience) as the preferred alternative.

                    Retrieves the list of available buyer intent topics that can be used
                    when creating BOMBOORA intent topic audiences. These intent topics represent different
                    buyer interest areas and purchasing signals that can be used for precise audience targeting.

                    WHEN TO USE:
                    - Always call this BEFORE suggesting or creating a Bombora audience to verify topic availability
                    - Discover available intent topics before creating a BOMBOORA intent topic audience
                    - Understand what buyer intent signals are available for targeting
                    - Build audiences based on specific buyer interests and purchasing signals
                    - Integrate intent topic selection into the audience creation flow

                    RETURNS:
                    List of available intent topics with their details including:
                    - Topic ID/name
                    - Topic description
                    - Available packages or categories
                    - Any additional metadata for targeting configuration

                    NEXT STEPS:
                    After retrieving intent topics, use the intent topic IDs with the audience
                    creation tool to create BOMBOORA intent topic based audiences.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false, and the description adds critical behavioral context beyond that: an empty topic list means Bombora is unavailable and should suppress Bombora audience suggestions, and the tool must be called before audience creation. No contradiction with annotations.

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

Conciseness3/5

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

The critical warning is front-loaded and the sections are clearly labeled, but the description is repetitive: the 'Retrieves' paragraph and several WHEN TO USE bullets restate the opening sentence and the IMPORTANT block. It is well-organized but not as tight as it could be.

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 zero-parameter, read-only tool with no output schema, the description covers the return shape (topic ID/name, description, packages/categories, metadata), the empty-list edge case, and the next step of using topic IDs in audience creation. Nothing essential is missing.

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?

The tool takes zero parameters and schema description coverage is 100%, so there are no parameter semantics for the description to add. The baseline of 4 for a zero-parameter tool applies, and the description appropriately focuses on output semantics instead.

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+resource ('Get available intent topics for BOMBOORA audience creation') and clearly distinguishes the tool from creation tools like create_bombora_audience and the firmographic alternative. It is immediately obvious what resource is being fetched and why.

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?

It explicitly instructs agents to call this tool first before suggesting or creating any Bombora audience, defines the empty-list result as 'Bombora is NOT available for this account,' and names create_firmographic_audience as the preferred alternative. The WHEN TO USE section reinforces this routing with concrete conditions.

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

All Metadata MCP Connector 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?