MCP Tool Directory

Approves an entire workstream — sets all 'Idea' status items to 'ApprovedForGeneration' and auto-assigns scheduled dates across the plan date range.

Partially updates a content item — only provided fields are changed.

Creates a new content item (article) with markdown content.

Generates an AI content brief for a content idea using web research. The brief specifies outline, key points, tone, CTAs — everything a writer needs. Stores the result in the idea's Brief field for review before content generation.

Merge or replace the brand's topics list.

Creates a new AI visibility monitoring query (prompt) for a brand.

Primary entry point. Returns brand details, keywords, topics, competitors, content summary (counts by status), active plan summaries, and recent timeline events. Call this first to understand the brand before using other tools.

Lists content items (articles) for a brand with pagination. Excludes the full body content for performance — use get_content_item to read the full article.

Resizes an existing image to fit within the given max dimensions, preserving aspect ratio. Creates a new image — the original is kept. Returns the new image URL.

Crops an existing image to a specific rectangle region. Creates a new image — the original is kept. Returns the new image URL. Use get_image_dimensions first if you need to know the source image size.

Gets brand analytics: sentiment scores, share of voice, mention rankings, and competitor mentions. Aggregated across all monitoring runs with optional filters.

Returns the width and height of an image. Useful before cropping to know the valid crop area.

Generates an AI image for a brand using Nano Banana (Gemini). The prompt can be plain text OR a JSON object. When using JSON, keys are merged with the brand's default image prompt (set in BrandKit visual style), with per-image keys taking precedence. Example JSON prompt: {"motif": "Cute robots working in a garden", "aspect": "16:9"}. Returns the public URL of the generated image.

Creates a content category for a brand. Categories are required for publishing articles. Returns the created category with its ID.

Triggers content generation for an approved content idea. Enqueues a job that runs research, writing, and editorial review. Creates a ContentItem with the generated markdown when done.

Batch status change for multiple content items (e.g. publish or archive several at once).

Lists all monitored AI visibility prompts for a brand.

Modifies an existing function-calling tool. Only fields that are explicitly provided will be updated (partial update). Returns the updated tool.

Lists all flows in the tenant.

Lists all function-calling tools in the tenant. Returns ID, name, description, tool type, and type-specific summary fields.

Lists recent ShuttleRequests (LLM invocations) for debugging. Optionally filter by flow name. Returns up to 50 recent runs.

Gets full flow details including prompt templates from the active version. Falls back to the latest version if no version is activated. Use environment parameter to specify which environment's active version to retrieve. If omitted and the flow has exactly one environment, it is auto-selected.

Updates a template's prompt text, response schema, and/or tool assignments in the active or latest version. If the version is locked, automatically forks it first (the fork is a draft — activate it via the UI or API). Falls back to the latest version if no version is activated. Returns confirmation with version ID and whether a fork was created.

Creates a new function-calling tool in the tenant. Provide name, description, parameters, toolType, and type-specific fields. toolType: External (REST endpoint), Virtual (provider-native like web_search), Agent (sub-agent), CritiqueLoop (producer+critic loop), Mcp (external MCP server). Returns the created tool with its ID.

This endpoint adds a service to an existing incident workflow trigger in PagerDuty. It allows you to associate a specific service with a trigger, enabling automated incident management processes for that service. Use this endpoint when you need to connect a service to an incident workflow, typically during the setup or modification of your incident response procedures. The endpoint requires the trigger's ID and the service's ID to make the association. It's important to note that this operation doesn't create new services or triggers, but rather links existing ones. Ensure that both the trigger and service exist in your PagerDuty account before making this call.

This endpoint analyzes and aggregates incident metrics across all escalation policies in PagerDuty. It allows for detailed filtering and customization of the analysis, enabling users to gain insights into incident patterns, response times, and escalation effectiveness. The endpoint is particularly useful for operational reviews, performance analysis, and identifying areas for improvement in incident management processes. It provides flexibility in data selection through various filters and supports different time-based aggregations for comprehensive reporting.

Retrieves and aggregates metrics for incidents across all services in PagerDuty. This endpoint allows for extensive filtering and customization of incident data, enabling detailed analysis of operational performance. It's particularly useful for generating reports, identifying trends, and assessing incident management efficiency over specified time periods. The endpoint supports various filtering criteria, time zone adjustments, and aggregation options, making it a powerful tool for both high-level overviews and granular incident analytics. However, users should be aware of the complexity of the filtering options and ensure they provide accurate parameters to obtain relevant data.

Associates multiple service dependencies in PagerDuty, allowing you to define relationships between supporting and dependent services. This endpoint is used to establish a hierarchical structure of services, which is crucial for effective incident management and impact analysis. It enables you to create multiple dependencies in a single API call, improving efficiency when setting up complex service relationships. Use this endpoint when you need to define or update the dependency structure of your services in PagerDuty, such as during initial setup, service restructuring, or when adding new services to your incident management workflow.

This endpoint associates a specific team with an automation action in PagerDuty. It allows you to link a team to an automated workflow, enabling better organization and management of automation actions within your incident response processes. Use this endpoint when you need to assign responsibility for an automation action to a particular team or when restructuring your automation workflows. The association helps in tracking, auditing, and managing permissions for automation actions across different teams in your organization. Note that this endpoint only creates the association; it does not create new teams or automation actions.

Retrieves the audit records for a specific escalation policy in PagerDuty. This endpoint allows users to access a detailed history of changes made to the escalation policy, including modifications to escalation rules, associated services, and on-call schedules. It's particularly useful for compliance tracking, troubleshooting, and understanding how the incident response process has been adjusted over time. The audit records provide transparency into who made changes, what was changed, and when the changes occurred, helping teams maintain accountability and optimize their incident management workflows.