DBM MCP Server - Generic cross-platform reporting and metrics
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
cross_platform_campaign_setupGuide for setting up a coordinated multi-platform campaign across DV360 (dv360-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), Meta Ads (meta-mcp), LinkedIn (linkedin-mcp), TikTok (tiktok-mcp), Pinterest (pinterest-mcp), Snapchat (snapchat-mcp), and Amazon DSP (amazon-dsp-mcp). Covers platfo…Guide for setting up a coordinated multi-platform campaign across DV360 (dv360-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), Meta Ads (meta-mcp), LinkedIn (linkedin-mcp), TikTok (tiktok-mcp), Pinterest (pinterest-mcp), Snapchat (snapchat-mcp), and Amazon DSP (amazon-dsp-mcp). Covers platfo…
No input schema was published for this tool.
totalBudgetTotal campaign budget across all platforms (e.g., '50000' for $50,000)Total campaign budget across all platforms (e.g., '50000' for $50,000)
No input schema was published for this tool.
objectiveCampaign objective: 'awareness', 'consideration', or 'conversion' (default: conversion)Campaign objective: 'awareness', 'consideration', or 'conversion' (default: conversion)
No input schema was published for this tool.
cross_platform_performance_comparisonGuide for comparing campaign performance across DV360 (via dbm-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), and Meta Ads (meta-mcp). Normalizes metrics, identifies top performers, and recommends budget reallocation.Guide for comparing campaign performance across DV360 (via dbm-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), and Meta Ads (meta-mcp). Normalizes metrics, identifies top performers, and recommends budget reallocation.
No input schema was published for this tool.
dateRangeDate range for comparison (e.g., LAST_7_DAYS, LAST_30_DAYS, or custom YYYY-MM-DD format)Date range for comparison (e.g., LAST_7_DAYS, LAST_30_DAYS, or custom YYYY-MM-DD format)
No input schema was published for this tool.
custom_query_workflowStep-by-step guide for building custom Bid Manager queries with the dbm_run_custom_query toolStep-by-step guide for building custom Bid Manager queries with the dbm_run_custom_query tool
No input schema was published for this tool.
advertiserIdDV360 Advertiser ID to queryDV360 Advertiser ID to query
No input schema was published for this tool.
queryGoalWhat you want to analyze (e.g., 'campaign performance', 'device breakdown', 'video metrics')What you want to analyze (e.g., 'campaign performance', 'device breakdown', 'video metrics')
No input schema was published for this tool.
pacing_performance_analysis_workflowStep-by-step guide for DV360 pacing assessment and performance deep-dive: check delivery pacing, analyze CPM/CTR/CPA/ROAS, identify historical trends, and recommend bid/budget adjustments via dv360-mcp.Step-by-step guide for DV360 pacing assessment and performance deep-dive: check delivery pacing, analyze CPM/CTR/CPA/ROAS, identify historical trends, and recommend bid/budget adjustments via dv360-mcp.
No input schema was published for this tool.
campaignIdDV360 Campaign ID to analyzeDV360 Campaign ID to analyze
No input schema was published for this tool.
focusAnalysis focus: 'pacing', 'performance', or 'both' (default: both)Analysis focus: 'pacing', 'performance', or 'both' (default: both)
No input schema was published for this tool.
dbm_run_custom_query_asyncExecute a custom Bid Manager API query asynchronously. Returns a task handle immediately —Execute a custom Bid Manager API query asynchronously. Returns a task handle immediately —
No input schema was published for this tool.
tool_schema_exploration_workflowStep-by-step workflow for exploring available MCP tools, prompts, and resources with minimal context usage.Step-by-step workflow for exploring available MCP tools, prompts, and resources with minimal context usage.
No input schema was published for this tool.
serverFocusServer to focus on: dbm-mcp, dv360-mcp, or both (default: both)Server to focus on: dbm-mcp, dv360-mcp, or both (default: both)
No input schema was published for this tool.
troubleshoot_reportDiagnostic workflow for debugging failed Bid Manager queries and common issuesDiagnostic workflow for debugging failed Bid Manager queries and common issues
No input schema was published for this tool.
errorMessageThe error message from the failed queryThe error message from the failed query
No input schema was published for this tool.
queryTypeType of query that failed (e.g., 'dbm_run_custom_query', 'dbm_get_campaign_delivery')Type of query that failed (e.g., 'dbm_run_custom_query', 'dbm_get_campaign_delivery')
No input schema was published for this tool.
17 of 17 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
DBM MCP Server - Generic cross-platform reporting and metrics
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
173 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+161 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.