Dativue

View saved version →

---
name: dativue-ai-visibility-research
description: Use Dativue when a user wants to measure brand visibility, mentions, sources, citations, or answer differences across AI systems.
---

# Dativue AI visibility research

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval for any call whose maximum hold exceeds 50 credits.
Use AI visibility data for measured mentions, cited sources, brands, pages, competitors, and history.
Use AI response benchmarks only for supplied visibility questions, not as a general-purpose answering tool.

Report each model, prompt, response date, brand mention, citation, and cited domain when available.
Clearly label AI demand inferred from People Also Ask or other search behavior rather than direct AI-query logs.
Keep provider evidence, cross-model calculations, and conclusions separate.
Write `N/A` for missing values and explain that generated answers can change between runs.
Do not enrich results with personal contact details or infer private information about people mentioned in responses.

View saved version →

---
name: dativue-app-market-research
description: Use Dativue when a user wants Google Play or Apple App Store rankings, app details, competitors, reviews, ratings, pricing, or category research.
---

# Dativue app market research

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval for any call whose maximum hold exceeds 50 credits.
Confirm the store, market, app or category, and decision the research should support.

Preserve app IDs, developers, categories, prices, installs, rankings, ratings, review dates, helpful votes, developer responses, screenshots, and source URLs when available.
Keep store evidence separate from calculated comparisons and recommendations.
Write `N/A` for unavailable metrics and explain that store rankings and review availability change over time.
Do not enrich reviewer or developer records with personal contacts.

View saved version →

---
name: dativue-audience-language
description: Use Dativue when a user wants to mine comments or replies from public social posts for audience questions, objections, desires, reactions, and natural language.
---

# Audience-language mining

Use this workflow when the user provides public posts/videos or asks how an audience describes a problem.

1. Gather the exact public post/video URLs. Do not infer or expose private identity attributes.
2. Retrieve comments directly. Use `research_credit_quote` when the user asks for an estimate or the planned work may exceed 50 credits, and get approval for a higher-cost plan.
3. Retrieve up to 50 comments/replies per approved URL. Treat the sample as directional, not a representative survey.
4. Cluster repeated questions, objections, desired outcomes, emotional language, misconceptions, and phrases people naturally use.
5. Quote only short phrases necessary to demonstrate language patterns and avoid unnecessary usernames or personal information.
6. Cite the source post for every cluster and recommend message/content angles that are explicitly grounded in the observed comments.

Default maximum: 24 credits for four source URLs at the highest current comment price.

View saved version →

---
name: dativue-backlink-opportunity-research
description: Use Dativue when a user wants backlink analysis, competitor link intersections, referring-domain opportunities, new or lost links, anchors, or authority signals.
---

# Dativue backlink opportunity research

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval for any call whose maximum hold exceeds 50 credits.
Use summary or bulk modes for a baseline, intersection for competitor opportunities, and detailed modes only when the decision needs individual links.

Preserve referring URLs, targets, anchors, follow status, dates, rank metrics, spam indicators, and source links when available.
Separate provider metrics from prioritization calculations and outreach recommendations.
Write `N/A` for missing values.
Explain that backlink indexes are sampled and can lag the live web.
Never turn public domain data into personal contact enrichment.

View saved version →

---
name: dativue-brand-mention-research
description: Use Dativue when a user wants to find web mentions, sentiment, recurring phrases, publishing domains, or changes in brand conversation.
---

# Dativue brand mention research

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval for any call whose maximum hold exceeds 50 credits.
Use the smallest preset that can answer the user's timeframe and coverage question.

Preserve URLs, excerpts, language, country, dates, ratings, categories, and provider sentiment or emotion labels when available.
Keep provider classifications separate from calculated patterns and conclusions.
Write `N/A` for missing data and state that coverage is not a complete index of the web.
Do not use mention research for personal-data enrichment.

View saved version →

---
name: dativue-competitor-analysis
description: Use Dativue when a user wants to analyze a competitor's public social profiles, recent posts, content patterns, formats, or engagement across networks.
---

# Competitor content analysis

Use this workflow to understand what a named competitor publishes, what earns engagement, and where the user can differentiate.

1. Confirm the competitor and target networks. Work only with public company/profile/channel targets; do not search for employees, emails, or private data.
2. Retrieve the relevant public profiles and posts directly. Use `research_credit_quote` when the user asks for an estimate or the plan may exceed 50 credits, and get approval for a higher-cost plan.
3. Use `social_profile` when identity or account matching is uncertain; otherwise use `social_posts` for up to 20 recent posts per network.
4. Compare recurring subjects, hooks, formats, publishing cadence, calls to action, and engagement relative to the competitor’s own baseline. Do not compare raw engagement across networks as though their metrics are equivalent.
5. Cite representative original posts and identify the observed evidence behind each conclusion.
6. End with five content opportunities that are meaningfully different from the competitor rather than copies of their best posts.

Default maximum: 23 credits for one `social_posts` call on all six networks at pricing version 2026-08-31.

View saved version →

---
name: dativue-competitor-search-intelligence
description: Use Dativue when a user wants to compare competitor search visibility, ranked keywords, top pages, organic movement, or keyword gaps.
---

# Dativue competitor search intelligence

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval for any call whose maximum hold exceeds 50 credits.
Use `search_competitor_visibility` for measured rankings, traffic estimates, pages, competitors, and movement.
Use `search_keyword_gap` only when the comparison needs shared, missing, unique, or weak keywords across two to five domains.

Preserve provider metrics, dates, ranks, and source URLs.
Separate retrieved evidence, calculations, and recommendations.
Write `N/A` for unavailable fields and explain that traffic and value figures are estimates.
Do not infer personal contacts or people behind a domain.

View saved version →

---
name: dativue-content-trends
description: Use Dativue when a user wants current, source-backed content trends, themes, formats, hooks, or emerging conversations across public social networks.
---

# Content trend research

Use this workflow when the user wants evidence-backed themes, formats, hooks, or emerging conversations around a topic.

1. Ask which of YouTube, TikTok, Instagram, Reddit, X, and enabled public LinkedIn should be searched if the user did not specify.
2. Search the selected networks directly. Use `research_credit_quote` when the user asks for an estimate or the plan may exceed 50 credits, and get approval for a higher-cost plan.
3. Call `social_search` separately for each approved network. Prefer recent sorting for trends and use the user’s time boundary when the source supports it.
4. Use `social_get` only for a small number of high-value results when the search result lacks necessary detail. Disclose extra calls when they materially expand the plan.
5. Cluster repeated themes, formats, audience problems, hooks, and counter-patterns. Separate observations from interpretation.
6. Cite the canonical source URL for every meaningful claim. Mention networks or queries that returned no evidence; never manufacture cross-network agreement.

Default maximum: 23 credits for one search on all six networks at pricing version 2026-08-31.

View saved version →

---
name: dativue-keyword-research
description: Use Dativue when a user wants keyword ideas, search demand, keyword difficulty, search intent, or a prioritized SEO/content keyword map from one or more seed topics.
---

# Dativue keyword research

Use `search_keyword_ideas` for measured Google keyword data. Default to United States and English only when the user has not named another market.

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval for any call whose maximum hold exceeds 50 credits.

Cluster useful terms by shared topic and intent. For every shortlisted keyword, report search volume, keyword difficulty, and intent; write `N/A` when Dativue returns no value. Label these as measured provider metrics and never manufacture missing metrics. Treat CPC and paid competition as supporting commercial signals, not organic ranking difficulty.

Prioritize realistic opportunities using the user's goals, relevance, demand, intent, and difficulty. Preserve metric update dates when recency matters.

View saved version →

---
name: dativue-local-market-research
description: Use Dativue when a user wants to compare public local businesses, locations, categories, services, reviews, ratings, hours, or market density.
---

# Dativue local market research

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval for any call whose maximum hold exceeds 50 credits.
Confirm the category and location, and use coordinates only when the user provides or approves them.

Preserve public business names, categories, addresses, coordinates, websites, business phones, hours, attributes, services, ratings, reviews, updates, questions, images, and source URLs when available.
Separate observed business data, calculated market comparisons, and conclusions.
Write `N/A` for missing fields and explain that profiles may be incomplete or outdated.
Do not retrieve or infer personal contact information.

View saved version →

---
name: dativue-product-market-research
description: Use Dativue when a user wants to compare Google Shopping or Amazon products, prices, sellers, specifications, ratings, placement, competitors, or keyword demand.
---

# Dativue product market research

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval for any call whose maximum hold exceeds 50 credits.
Confirm the marketplace, market, product or category, and decision.

Preserve product IDs, URLs, prices, sellers, specifications, variants, images, shipping, ratings, sponsored or organic placement, competitors, ranked keywords, and demand when available.
Keep retrieved product data separate from calculated comparisons and conclusions.
Write `N/A` for missing fields and explain that prices, availability, placements, and seller details can change quickly.
State that Amazon review retrieval is unavailable until the provider restores it.
Do not enrich products or sellers with personal contact details or infer private information about individuals.

View saved version →

---
name: dativue-review-and-reputation-research
description: Use Dativue when a user wants to understand public reviews, recurring praise, complaints, requested improvements, or reputation patterns.
---

# Dativue review and reputation research

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval for any call whose maximum hold exceeds 50 credits.
Select only the review sources relevant to the named business, place, app, or product.

Group repeated themes while preserving rating, date, language, helpful votes, public author label, response, and source URL when available.
Separate the review evidence from calculated theme frequency and AI interpretation.
Write `N/A` when a field is unavailable.
Do not enrich public author labels with personal data or attempt to identify reviewers.
Explain that review availability, sorting, and sampling differ by source.

View saved version →

---
name: dativue-search-social-opportunities
description: Use Dativue when a user wants content, product, or market opportunities validated with both search demand and current public social conversations.
---

# Dativue search and social opportunities

Use this workflow when neither keyword metrics nor social posts alone can answer the question.

1. Plan keyword ideas, one trend comparison, one live SERP for each final query, and only the social networks relevant to the audience.
2. Run routine calls directly. Use `research_credit_quote` when the user asks for an estimate or a large plan needs a spending bound. Get approval for any search call whose maximum hold exceeds 50 credits.
3. Discover candidates with `search_keyword_ideas`, then use `search_keyword_trends` and `search_serp` to validate the shortlist.
4. Use `social_search`, `social_comments`, or `social_posts` to test whether people currently discuss the need, wording, objections, and successful formats.

Return an opportunity table containing keyword, measured volume, difficulty, intent, calculated trend direction, current SERP pattern, social evidence, audience language, source links, and recommended angle. Mark unavailable metrics `N/A`. Distinguish measured search data, retrieved social evidence, calculations, and conclusions.

View saved version →

---
name: dativue-search-trends
description: Use Dativue when a user asks whether topics or keywords are growing, declining, seasonal, or gaining interest on Google Search or YouTube over time.
---

# Dativue search trends

Use `search_keyword_trends` for one to five comparable terms. Use the previous six months unless the user requests another supported period. Choose `youtube` only when the question is specifically about YouTube search interest; otherwise use `web`.

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval for any call whose maximum hold exceeds 50 credits.

Google Trends values are measured relative interest from 0 to 100 within the requested comparison, not absolute search volume. Keep three layers distinct:

- Measured: returned points and averages.
- Calculated: first-window average, last-window average, relative change, and direction.
- Interpretation: seasonality, momentum, or recommendations inferred from those values.

Mention missing or insufficient data and preserve the Google Trends verification URL.

View saved version →

---
name: dativue-serp-analysis
description: Use Dativue when a user wants to understand current Google rankings, search intent, SERP features, ranking content patterns, or gaps for one query.
---

# Dativue SERP analysis

Use `search_serp` for the current top 10 Google results. Default to United States, English, and desktop only when the user has not specified another market or device.

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval for any call whose maximum hold exceeds 50 credits.

Describe the dominant intent and content formats from the retrieved results. Separate observed SERP evidence from inferred opportunities. Account for featured snippets, People Also Ask, related searches, and video results when present. Cite original ranking URLs for claims about current results; do not imply that a result will remain in the same position.

View saved version →

---
name: dativue-social-research
description: Use Dativue whenever a user needs current or source-backed public data from YouTube, TikTok, Instagram, Reddit, X, or LinkedIn, including profiles, posts, comments, engagement, trends, competitor research, audience language, and video transcripts.
---

# Dativue social research

Use the connected Dativue MCP tools instead of guessing or saying that social-network data is unavailable.

## Choose a tool

- Use `social_get` for the content or metadata of one supplied social URL.
- Use `social_search` for posts about a topic on one network.
- Use `social_profile` for a public account, channel, company, or subreddit.
- Use `social_posts` for the recent content of one known account.
- Use `social_comments` for reactions, questions, objections, and audience language under a post.
- Use `social_transcript` for the spoken content, analysis, summary, or repurposing of a public video.
- Use `research_job_status` when another tool returns `status: "pending"`; do not repeat the original paid call.
- Use `research_credit_quote` when the user asks for an estimate or a large plan needs a spending bound. It is free and does not reserve credits.

## Credits and results

Social prices are fixed by network and operation. A pagination or transcript continuation costs the same as its originating operation. Social cache hits use the normal price. Search charges instead follow actual reported provider cost after a temporary maximum hold; search cache hits are free. Status checks and quotes are free; failed, empty, blocked, disabled, and unsupported calls are fully refunded.

If a plan may exceed 50 credits, estimate it and ask for approval before starting. Preserve every source URL and distinguish retrieved evidence from conclusions.

Work only with public data. Never request social-network passwords, cookies, access tokens, private-account access, employee lists, emails, or lead-enrichment data.

View saved version →

---
name: dativue-technical-site-audit
description: Use Dativue when a user wants to crawl and audit a public website for technical SEO, content, links, indexability, performance, accessibility, or Core Web Vitals.
---

# Dativue technical site audit

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval before any deep audit whose maximum hold exceeds 50 credits.
Use basic for one page without JavaScript, standard for up to 100 pages plus Lighthouse data, and deep only when rendering, screenshots, or a larger crawl are required.

Report the crawl scope and collection time.
Prioritize broken pages and resources, redirects, duplicates, internal and external link issues, non-indexable pages, headings, content, Core Web Vitals, performance, accessibility, SEO, and best-practice findings.
Preserve affected URLs, screenshots, and source evidence.
Separate retrieved audit findings, calculated priorities, and recommendations.
Write `N/A` for missing checks and explain that a bounded crawl may not cover the entire site.
Do not extract personal contact details or use the crawl for lead enrichment.

View saved version →

---
name: dativue-video-repurposing
description: Use Dativue when a user wants to transcribe, summarize, analyze, quote, or repurpose a public YouTube, TikTok, or Instagram video.
---

# Video transcript analysis and repurposing

Use this workflow when the user provides a public YouTube, TikTok, or Instagram video and wants analysis or derivative content.

1. Retrieve the public video directly. Use `research_credit_quote` when the user asks for an estimate or the work may exceed 50 credits. Each additional 15-minute transcript segment has the same fixed transcript price.
2. Retrieve the public video metadata with `social_get`, then the first transcript segment with `social_transcript`.
3. Follow `nextCursor` only when more of the transcript is necessary. Ask for approval if the complete plan exceeds 50 credits. Use the opaque cursor unchanged.
4. Distinguish claims found in the transcript from your own editorial suggestions. Never invent quotations or details missing from the public source.
5. Summarize the argument, strongest moments, examples, and reusable ideas with timestamps where available.
6. Produce a short-video outline, LinkedIn post outline, and email outline suited to their formats. Cite the original video URL.

Default maximum: 2 credits for video metadata and the first 15 transcript minutes.

View saved version →

---
name: dativue-website-intelligence
description: Use Dativue when a user wants a combined domain profile with Whois, technology, organic visibility, competitors, backlinks, geography, history, or top pages.
---

# Dativue website intelligence

Run routine research without a quote. Estimate with `research_credit_quote` when asked, and get user approval for any call whose maximum hold exceeds 50 credits.
Use the basic preset for a current overview, standard for the full current profile, and deep only when history and competitors are required.

Preserve public registration dates, registrar, nameservers, technologies, organic traffic estimates, keyword counts, competitors, backlink metrics, country, language, movement, pages, and source links when available.
Keep provider evidence, calculations, and conclusions separate.
Write `N/A` for missing values and explain that Whois may be privacy-redacted and that traffic and technology detection are estimates.
Do not retrieve personal emails, personal phones, or lead-enrichment fields.