← Back to all apps

Brand24

Businessby Brand24 Global Inc.

The Brand24 app in ChatGPT lets marketing and PR teams instantly explore brand mentions, sentiment, and media coverage using simple prompts. Summarize conversations, track brand reputation, analyze trends over time, and uncover key discussion sources across social media, news, blogs, and forums without leaving ChatGPT.

From spotting emerging issues to understanding audience perception and campaign impact, ChatGPT interprets Brand24 data in real time, helping marketers and PR specialists move from monitoring to insight and action with no extra setup.

8ChatGPT Tools
Brand24 Global Inc.Developer
BusinessCategory

Available Tools

Brand24 Account Events

brand24_account_events
Full Description

Get important events (anomalies) from ALL Brand24 projects in your account.

Retrieves significant moments across all your projects when something extraordinary happened - mention spikes, sentiment changes, viral hashtags, or other anomalies. Provides account-wide overview.

Args:

  • response_format (string, optional): Output format - "json" or "markdown" (default: "markdown")

Returns: Array of anomaly objects (events from different projects mixed chronologically): [ { "anomaly_date": string, "project_id": number, "project_name": string, "description": string, "peak_mentions": number, "peak_reach": number, "is_hashtag_anomaly": boolean, "is_user_discussion_anomaly": boolean, "is_emotional_anomaly": boolean, "is_news_anomaly": boolean, "is_social_media_anomaly": boolean, "is_non_social_media_anomaly": boolean } ]

Usage Examples:

  • Use when: "What significant events happened across all my Brand24 projects?"

→ params: {}

  • Use when: "Show me all recent anomalies across monitored brands"

→ params: {}

  • Use when: "Any viral moments in any of my projects recently?"

→ params: {}

  • Use when: "Overview of all important brand events this month"

→ params: {}

  • Don't use when: Only want events for ONE project → use brand24_project_events
Parameters (0 required, 1 optional)
Optional
response_formatstring

Output format: 'json' for machine-readable or 'markdown' for human-readable

Options:jsonmarkdown
Default: markdown

Brand24 Get Projects

brand24_get_projects
Full Description

Get list of Brand24 projects.

Retrieves all projects available in the Brand24 account. User ID is automatically extracted from JWT token.

Args:

  • response_format (string, optional): Output format - "json" or "markdown" (default: "markdown")

Returns: Array of project objects [ { "project_id": number, "project_name": string } ]

Usage Examples:

  • Use when: "List all my Brand24 projects"

→ params: {}

  • Use when: "What projects do I have access to?"

→ params: {}

  • Use when: "Show me all available projects"

→ params: {}

Parameters (0 required, 1 optional)
Optional
response_formatstring

Output format: 'json' for machine-readable or 'markdown' for human-readable

Options:jsonmarkdown
Default: markdown

Brand24 Get Semantic Search Mentions

brand24_get_semantic_search_mentions
Full Description

Understand what people are saying about a topic through semantic analysis of conversations.

This tool answers questions about the MEANING and CONTENT of discussions, not about getting latest mentions or statistics. Uses semantic search to analyze what people are actually saying about a topic, brand, product, or concept by understanding the context and meaning of conversations.

IMPORTANT: This tool focuses on understanding the semantic meaning and content of what people are discussing. It does NOT provide quantitative data, statistics, counts, or latest mention lists. Use this when you need to understand WHAT people are saying, not HOW MANY mentions exist.

Args:

  • query (string, required): The topic or subject to understand what people are saying about (e.g., "Witcher", "product launch", "customer service")
  • projectId (number, required): The project ID
  • dateRange (object, optional): Date range with from and to dates (Date format: YYYY-MM-DD). Dates are automatically normalized to current year if outdated. Defaults to last 30 days if not provided
  • mentionsLimit (number, optional): Maximum number of mentions to analyze. Defaults to 10, maximum is 30

Returns: Mentions object with results array containing mention content and details. Focus on the content/text of mentions to understand what people are saying.

Usage Examples:

  • Use when: "What are people saying about Witcher?"

→ params: { query: "Witcher", projectId: 123, dateRange: { from: "2025-01-01", to: "2025-01-31" } }

  • Use when: "What do people think about the product launch?"

→ params: { query: "product launch", projectId: 123, dateRange: { from: "2025-01-01", to: "2025-01-31" }, mentionsLimit: 20 }

  • Use when: "What are customers saying about our service?"

→ params: { query: "customer service", projectId: 123, dateRange: { from: "2025-01-01", to: "2025-01-31" } }

Do NOT use for:

  • Getting latest mentions (use brand24_get_mentions instead)
  • Getting statistics or counts
  • Getting quantitative data
Parameters (2 required, 2 optional)
Required
projectIdnumber

The project ID to search mentions in

querystring

The search query or topic to find mentions about (e.g., "Adobe", "product launch", "customer service")

Optional
dateRange

Date range object with 'from' and 'to' fields in YYYY-MM-DD format. **CRITICAL: Current year is 2026** ⚠️ For recent/current data, always use 2026, not 2025 or earlier years. ✅ If user explicitly requests historical data (e.g., "data from 2023"), honor their specified year. **Common patterns for recent data (use 2026):** - Last 30 days: { "from": "2026-MM-DD", "to": "2026-MM-DD" } - Last month: { "from": "2026-MM-01", "to": "2026-MM-30" } - This year to date: { "from": "2026-01-01", "to": "2026-MM-DD" } - Custom recent range: { "from": "2026-01-15", "to": "2026-03-20" } **For historical queries:** - User says "data from 2023": Use 2023, e.g., { "from": "2023-01-01", "to": "2023-12-31" } - User says "Q1 2024": Use 2024, e.g., { "from": "2024-01-01", "to": "2024-03-31" } When user requests relative dates without specifying a year (like "last 30 days", "this month"), compute month/day from today but use 2026. Dates are automatically normalized if outdated year is used by mistake. Default: last 30 days if not specified.

mentionsLimitnumber

Maximum number of mentions to return. Defaults to 10, maximum is 30 (optional)

Brand24 Project Events

brand24_project_events
Full Description

Get important events (anomalies) from a specific Brand24 project.

Retrieves significant moments when something extraordinary happened - mention spikes, sentiment changes, viral hashtags, or other anomalies. Queries events for ONE project by name.

If the specified project name is not found, the tool will return a list of all available projects in your account, allowing automatic selection of the correct project name.

Args:

  • projectName (string): Brand24 project name to fetch events for

Examples: "Nike", "Apple Brand Monitor", "Tesla Social Media"

  • response_format (string, optional): Output format - "json" or "markdown" (default: "markdown")

Returns: On success: Array of anomaly objects [ { "anomaly_date": string, "project_id": number, "project_name": string, "description": string, "peak_mentions": number, "peak_reach": number, "is_hashtag_anomaly": boolean, "is_user_discussion_anomaly": boolean, "is_emotional_anomaly": boolean, "is_news_anomaly": boolean, "is_social_media_anomaly": boolean, "is_non_social_media_anomaly": boolean } ]

On project not found: Object with available projects list { "error": string, "requestedProjectName": string, "availableProjects": [ { "project_id": number, "project_name": string } ] }

Usage Examples:

  • Use when: "What significant events happened for the Nike project?"

→ params: { projectName: "Nike" }

  • Use when: "Show me recent anomalies for our Tesla monitoring project"

→ params: { projectName: "Tesla Social Media" }

  • Use when: "Have there been any viral moments for Apple recently?"

→ params: { projectName: "Apple Brand Monitor" }

  • Use when: "What caused the spike in mentions last week for project X?"

→ params: { projectName: "X" }

  • Use when: "What is the discussion about the Microsoft brand?"

→ params: { projectName: "Microsoft" }

  • Don't use when: Want events across ALL projects → use brand24_account_events
Parameters (1 required, 1 optional)
Required
projectNamestring

The project name to analyze (e.g., 'Nike', 'Apple', 'Tesla')

Optional
response_formatstring

Output format: 'json' for machine-readable or 'markdown' for human-readable

Options:jsonmarkdown
Default: markdown

Brand24 Project Sources

brand24_project_sources
Full Description

Get insights about project sources - either mentions from top authors or source category breakdown.

This tool provides two operations to analyze project sources:

1. Top Authors: Returns mentions from the most popular authors based on engagement metrics (followers, interactions, reach). Useful for identifying key influencers and content creators. 2. Source Categories: Returns project source categories (e.g., Blogs, News, Social Media, Forums) with mention counts for each category. Helps understand where discussions are happening.

Args:

  • operationName (string, required): Which operation to execute - "getMentionsTopAuthors" or "getProjectSourceCategories"
  • projectId (number, required): The project ID
  • dateRange (object, required): Date range with from and to dates (Date format: YYYY-MM-DD). Dates are automatically normalized to current year if outdated.
  • filters (object, optional): Mention filters object. See variableDescriptions for filters property for details. Default values are automatically applied when filters are not provided
  • source (enum, optional): Source type filter (only for getMentionsTopAuthors). Values: mentions_tab, analysis_tab, summary_tab, comparison_tab, sources_tab, influencers_tab, lab_tab

Returns:

  • getMentionsTopAuthors: Array of Mention objects from top authors
  • getProjectSourceCategories: Array of ProjectSourceCategory objects with id and count

Usage Examples:

  • Use when: "Get mentions from top authors for project 123"

→ params: { operationName: "getMentionsTopAuthors", projectId: 123, dateRange: { from: "2025-01-01", to: "2025-01-31" } }

  • Use when: "Show me source categories breakdown"

→ params: { operationName: "getProjectSourceCategories", projectId: 123, dateRange: { from: "2025-01-01", to: "2025-01-31" } }

  • Use when: "Get top authors from social media sources"

→ params: { operationName: "getMentionsTopAuthors", projectId: 123, dateRange: { from: "2025-01-01", to: "2025-01-31" }, source: "sources_tab" }

Parameters (2 required, 3 optional)
Required
operationNamestring

Which operation to execute

Options:getMentionsTopAuthorsgetProjectSourceCategories
projectIdnumber

The project ID to get top authors mentions for

Optional
dateRange

Date range object with 'from' and 'to' fields in YYYY-MM-DD format. **CRITICAL: Current year is 2026** ⚠️ For recent/current data, always use 2026, not 2025 or earlier years. ✅ If user explicitly requests historical data (e.g., "data from 2023"), honor their specified year. **Common patterns for recent data (use 2026):** - Last 30 days: { "from": "2026-MM-DD", "to": "2026-MM-DD" } - Last month: { "from": "2026-MM-01", "to": "2026-MM-30" } - This year to date: { "from": "2026-01-01", "to": "2026-MM-DD" } - Custom recent range: { "from": "2026-01-15", "to": "2026-03-20" } **For historical queries:** - User says "data from 2023": Use 2023, e.g., { "from": "2023-01-01", "to": "2023-12-31" } - User says "Q1 2024": Use 2024, e.g., { "from": "2024-01-01", "to": "2024-03-31" } When user requests relative dates without specifying a year (like "last 30 days", "this month"), compute month/day from today but use 2026. Dates are automatically normalized if outdated year is used by mistake. Default: last 30 days if not specified.

filtersobject

Optional mention filters object. Properties: va (number, spam level: 0=all, 1=medium, 2=high, 3=low), rt (number[], source IDs: 1=Twitter/X, 2=Instagram, 3=Blogs, 4=Videos, 5=Facebook, 6=Forums, 7=News, 8=Web, 9=Podcasts, 11=TikTok), se (string[], sentiments: positive/negative/neutral), imp (boolean|null, important only), vi (boolean|null, visited), gr (number[], tag IDs), cxs (number[], context search IDs), sq (string, text search), do (string, domain), lem (boolean, include lemmas), ctr (string[], country codes ISO 3166-1 alpha-2), nctr (boolean, exclude geolocations), is (number[], influencer score range [min, max] 0-10), i (number[], intent IDs 0-11), tp (number|null, topic ID), anom (string, anomaly type), lang (string[], language codes ISO 639-1), nlang (boolean, exclude languages), aue (number|null, Audiense audience ID), htg (string, hashtag), mt (boolean, muted mentions), mtri (number|null, mute rule ID), em (number[], emotion IDs 0-6). Default values are automatically applied.

source

Source type filter: mentions_tab, analysis_tab, summary_tab, comparison_tab, sources_tab, influencers_tab, or lab_tab (optional)

Brand24 Project Stats

brand24_project_stats
Full Description

Get daily statistics (mentions count, positive mentions, negative mentions, reach) for a specific Brand24 project.

Retrieves daily aggregated metrics showing mentions count, reach (sum of social and non-social media), positive mentions, and negative mentions per day. Queries statistics for ONE project by name.

If the specified project name is not found, the tool will return a list of all available projects in your account, allowing automatic selection of the correct project name.

Args:

  • projectName (string): Brand24 project name to fetch statistics for

Examples: "Nike", "Apple Brand Monitor", "Tesla Social Media"

  • dateFrom (string, optional): Start date in YYYY-MM-DD format (default: 30 days ago)
  • dateTo (string, optional): End date in YYYY-MM-DD format (default: today)
  • response_format (string, optional): Output format - "json" or "markdown" (default: "markdown")

Returns: On success: Statistics object { "projectId": string, "projectName": string, "dateFrom": string, "dateTo": string, "stats": [ { "date": string, "mentionsCount": number | null, "positiveMentions": number | null, "negativeMentions": number | null, "reach": number | null } ] }

On project not found: Object with available projects list { "error": string, "requestedProjectName": string, "availableProjects": [ { "project_id": number, "project_name": string } ] }

Usage Examples:

  • Use when: "What are the statistics for the Nike project?"

→ params: { projectName: "Nike" }

  • Use when: "Show me stats for our Tesla project from last week"

→ params: { projectName: "Tesla", dateFrom: "YYYY-MM-DD", dateTo: "YYYY-MM-DD" }

  • Use when: "How many mentions did we get per day for Apple project?"

→ params: { projectName: "Apple" }

  • Use when: "What is the average reach for the Adidas project?"

→ params: { projectName: "Adidas" }

  • Don't use when: Need significant events/anomalies → use brand24_project_events
  • Don't use when: Need understand what the discussion about the project is → use brand24_project_events
Parameters (1 required, 3 optional)
Required
projectNamestring

The project name to analyze (e.g., 'Nike', 'Apple', 'Tesla')

Optional
dateFromstring

Start date in YYYY-MM-DD format. Dates are automatically normalized to current year if outdated. Defaults to 30 days ago.

dateTostring

End date in YYYY-MM-DD format. Dates are automatically normalized to current year if outdated. Defaults to today.

response_formatstring

Output format: 'json' for machine-readable or 'markdown' for human-readable

Options:jsonmarkdown
Default: markdown

Brand24 Quick Popularity Comparison

brand24_quick_popularity_comparison
Full Description

Quickly compare popularity of brands or other entities (people names, sports clubs, etc.) on the Internet. This tool provides a quick comparison but is NOT as detailed or accurate as Brand24 Project Stats data.

IMPORTANT: This tool should be used when you want to quickly compare how two or more brands or entities are popular in the Internet relative to each other. The data is less detailed and accurate than Brand24 Project Stats.

When to use:

  • Quick comparison of popularity between brands or other entities (people names, sports clubs, anything discussed on the Internet)
  • When you need a fast overview without detailed metrics
  • As a backup option when there's no Brand24 project with the given brand/entity name in your account

When NOT to use:

  • When you need detailed, accurate data → use brand24_project_stats instead
  • When you have a Brand24 project for the brand/entity → use brand24_project_stats for better accuracy
  • When you need historical trends, sentiment analysis, or event tracking → use brand24_project_stats or brand24_project_events

Args:

  • brandNames (string[]): Array of brand/entity names to compare (1-10 items)

Examples: ["Nike", "Adidas", "Puma"], ["Apple", "Microsoft", "Google"], ["Lionel Messi", "Cristiano Ronaldo"], ["Real Madrid", "Barcelona"]

  • countryCode (string, optional): ISO 3166-1 alpha-2 country code (applies to all brands)

Examples: "US", "GB", "DE", "PL"

  • response_format (string, optional): Output format - "json" or "markdown" (default: "markdown")

Returns: { "totalBrands": number, "successCount": number, "failureCount": number, "countryCode"?: string, // Present if countryCode was provided "results": [ { "brandName": string, "status": "success" | "error", "brandSize"?: number, // Present if status is "success" "error"?: string // Present if status is "error" } ] }

Usage Examples:

  • Use when: "Quickly compare popularity of Nike, Adidas, and Puma"

→ params: { brandNames: ["Nike", "Adidas", "Puma"] }

  • Use when: "How popular are Apple and Microsoft compared to each other?"

→ params: { brandNames: ["Apple", "Microsoft"] }

  • Use when: "Compare popularity of two football players"

→ params: { brandNames: ["Lionel Messi", "Cristiano Ronaldo"] }

  • Use when: "Quick comparison of sports clubs"

→ params: { brandNames: ["Real Madrid", "Barcelona", "Manchester United"] }

  • Use when: "Compare popularity of brands in a specific country"

→ params: { brandNames: ["Apple", "Microsoft", "Google"], countryCode: "US" }

  • Don't use when: Need detailed data about project → use brand24_project_stats
  • Don't use when: More than 10 entities → split into multiple requests
Parameters (1 required, 2 optional)
Required
brandNamesarray

Array of brand/entity names to compare (e.g., ['Nike', 'Apple', 'Tesla'] or ['Lionel Messi', 'Cristiano Ronaldo'] or ['Real Madrid', 'Barcelona'])

Optional
countryCodestring

ISO 3166-1 alpha-2 country code (e.g., 'US', 'GB', 'DE', 'PL') - applies to all brands

response_formatstring

Output format: 'json' for machine-readable or 'markdown' for human-readable

Options:jsonmarkdown
Default: markdown

Brand24 Topics Overview

brand24_topics_overview
Full Description

Get Topic Analysis overview for a project (Lab24 feature).

Returns comprehensive topic analysis data that identifies main themes and topics discussed in project mentions. Uses AI to detect and categorize topics, providing insights into what discussions are about.

Features:

  • Topic detection: Automatically identifies main topics/themes in mentions
  • Sentiment distribution: Shows sentiment breakdown (positive/negative/neutral) per topic
  • Share of voice: Percentage of mentions each topic represents
  • Reach metrics: Total reach for each topic
  • Topics overview: List of detected topics with descriptions, emoticons, and metrics

Args:

  • projectId (number, required): The project ID
  • dateRange (object, required): Date range with from and to dates (Date format: YYYY-MM-DD). Dates are automatically normalized to current year if outdated.
  • filters (object, optional): Mention filters object. See variableDescriptions for filters property for details. Default values are automatically applied when filters are not provided

Returns:

TopicsOverviewResults object containing:

  • status: Analysis status
  • overview: Array of TopicsOverview objects with internalId, name, description, emoticon, mentions count, reach, sentiment pie chart, and shareOfVoice
  • topicsShare: Pie chart data showing distribution of topics
  • accessedProjects: List of projects with topic analysis access
  • limit: Maximum number of topics returned

Usage Examples:

  • Use when: "What topics are being discussed about my project?"

→ params: { projectId: 123, dateRange: { from: "2025-01-01", to: "2025-01-31" } }

  • Use when: "Show me topic analysis for project 123"

→ params: { projectId: 123, dateRange: { from: "2025-01-01", to: "2025-01-31" } }

  • Use when: "What are the main themes in mentions from last month?"

→ params: { projectId: 123, dateRange: { from: "2024-12-01", to: "2024-12-31" } }

Parameters (1 required, 2 optional)
Required
projectIdnumber

The project ID to get topic analysis for

Optional
dateRange

Date range object with 'from' and 'to' fields in YYYY-MM-DD format. **CRITICAL: Current year is 2026** ⚠️ For recent/current data, always use 2026, not 2025 or earlier years. ✅ If user explicitly requests historical data (e.g., "data from 2023"), honor their specified year. **Common patterns for recent data (use 2026):** - Last 30 days: { "from": "2026-MM-DD", "to": "2026-MM-DD" } - Last month: { "from": "2026-MM-01", "to": "2026-MM-30" } - This year to date: { "from": "2026-01-01", "to": "2026-MM-DD" } - Custom recent range: { "from": "2026-01-15", "to": "2026-03-20" } **For historical queries:** - User says "data from 2023": Use 2023, e.g., { "from": "2023-01-01", "to": "2023-12-31" } - User says "Q1 2024": Use 2024, e.g., { "from": "2024-01-01", "to": "2024-03-31" } When user requests relative dates without specifying a year (like "last 30 days", "this month"), compute month/day from today but use 2026. Dates are automatically normalized if outdated year is used by mistake. Default: last 30 days if not specified.

filtersobject

Optional mention filters object. Properties: va (number, spam level: 0=all, 1=medium, 2=high, 3=low), rt (number[], source IDs: 1=Twitter/X, 2=Instagram, 3=Blogs, 4=Videos, 5=Facebook, 6=Forums, 7=News, 8=Web, 9=Podcasts, 11=TikTok), se (string[], sentiments: positive/negative/neutral), imp (boolean|null, important only), vi (boolean|null, visited), gr (number[], tag IDs), cxs (number[], context search IDs), sq (string, text search), do (string, domain), lem (boolean, include lemmas), ctr (string[], country codes ISO 3166-1 alpha-2), nctr (boolean, exclude geolocations), is (number[], influencer score range [min, max] 0-10), i (number[], intent IDs 0-11), tp (number|null, topic ID), anom (string, anomaly type), lang (string[], language codes ISO 639-1), nlang (boolean, exclude languages), aue (number|null, Audiense audience ID), htg (string, hashtag), mt (boolean, muted mentions), mtri (number|null, mute rule ID), em (number[], emotion IDs 0-6). Default values are automatically applied.