Skip to main content
Glama

list_sns_topics

Retrieve all Amazon SNS topics from your AWS account to manage messaging services and monitor topic configurations.

Instructions

Lists all SNS topics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Executes ListTopicsCommand via SNSClient to list all SNS topics and returns their ARNs as JSON.
    if (name === "list_sns_topics") {
        const command = new ListTopicsCommand({});
        const response = await snsClient.send(command);
        const topics = response.Topics?.map(t => ({ TopicArn: t.TopicArn })) || [];
        return { content: [{ type: "text", text: JSON.stringify(topics, null, 2) }] };
    }
  • src/index.ts:686-692 (registration)
    Registers the list_sns_topics tool in ListTools handler with description and empty input schema.
        name: "list_sns_topics",
        description: "Lists all SNS topics.",
        inputSchema: {
            type: "object",
            properties: {}
        }
    },
  • Initializes the SNSClient instance used by the list_sns_topics handler.
    const snsClient = new SNSClient({});
  • Imports SNSClient and ListTopicsCommand required for the tool implementation.
    import { SNSClient, ListTopicsCommand, ListSubscriptionsCommand } from "@aws-sdk/client-sns";
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Lists all SNS topics' but doesn't disclose behavioral traits such as pagination, rate limits, authentication requirements, or what 'all' entails (e.g., region-specific, account-wide). This is a significant gap for a tool with no annotation coverage.

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 a single, efficient sentence with zero waste. It's front-loaded and appropriately sized for a simple list tool, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema) and lack of annotations, the description is incomplete. It doesn't address behavioral aspects like scope, pagination, or error handling, which are important for an agent to use it correctly in a cloud environment.

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 has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but this is appropriate given the lack of parameters, warranting a baseline score of 4.

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 'Lists all SNS topics' clearly states the verb ('Lists') and resource ('SNS topics'), making the tool's purpose immediately understandable. It distinguishes from siblings by specifying SNS topics, though it doesn't explicitly differentiate from other list tools beyond the resource type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context for use, or comparison with other list tools in the sibling set (e.g., list_s3_buckets, list_lambda_functions).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bhaveshopss/MCP-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server