microsoft_ads_developer_feedback

Description

Submit feedback about missing tools, improvements needed, bugs encountered, or workflow gaps discovered while helping a user with Microsoft Advertising data. This is the correct, expected action when a Microsoft Ads capability is missing or broken — reach for it directly rather than just apologizing or giving up. Use this when: - A user request cannot be fulfilled because a tool doesn't exist — set feedback_type='missing_tool' and describe the missing capability and why the user needs it. When the user explicitly asks you to submit/file/report feedback about a gap or missing feature, that is a direct instruction: ALWAYS call this tool to record it. Do this even if you suspect a tool for the capability might already exist — submit the feedback as asked, and you may note the possibly-relevant existing tool inside the feedback message. Do NOT refuse, and do NOT stop at only searching the toolset. - An existing tool returned incorrect or incomplete data — set feedback_type='bug' and include tool_name. - A multi-step workflow is unnecessarily complex due to toolset limitations — feedback_type='workflow_gap'. - You discovered a Microsoft Ads API behaviour that the toolset doesn't handle. Submitting is low-cost and always safe: it records the feedback and returns status=submitted. When in doubt about whether a gap is worth reporting, report it. Do NOT use for: - User-facing API errors (auth errors, account permission errors, rate limits) - Questions about Microsoft Advertising strategy — that's outside this tool's scope - General conversation

Usage

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "microsoft_ads_developer_feedback",
    "arguments": {
      "feedback_type": "missing_tool",
      "message": "No tool to list Audience segments by account. User wanted to see which LinkedIn profile targeting segments are active. microsoft_ads_list_ad_groups returns ad group names but not audience targeting details.",
      "reason": "User asked about audience targeting but no tool covers it"
    }
  }
}

hopkin microsoft developer-feedback send

{
  "mcpServers": {
    "microsoft-ads": {
      "url": "https://microsoft.mcp.hopkin.ai",
      "transport": "sse"
    }
  }
}

Parameters

Examples

{
  "feedback_type": "missing_tool",
  "message": "No tool to list Audience segments by account. User wanted to see which LinkedIn profile targeting segments are active. microsoft_ads_list_ad_groups returns ad group names but not audience targeting details.",
  "reason": "User asked about audience targeting but no tool covers it"
}

{
  "feedback_type": "bug",
  "tool_name": "microsoft_ads_get_performance_report",
  "message": "Report for date_preset=LastMonth returned 0 rows even though the account has active campaigns with traffic. The reportRequestId was returned but downloadUrl was null after 5 retries.",
  "reason": "Encountered null download URL bug even with retry logic"
}

{
  "feedback_type": "workflow_gap",
  "message": "To compare two campaigns side-by-side the user must make two separate microsoft_ads_get_performance_report calls then mentally compare. A single tool accepting multiple campaign_ids and returning a comparison table would be much better.",
  "reason": "User wanted campaign-level comparison; no efficient path exists"
}

{
  "feedback_type": "improvement",
  "tool_name": "microsoft_ads_list_keywords",
  "message": "list_keywords does not return the keyword bid amount or Quality Score sub-components (KeywordRelevance, LandingPageRelevance, LandingPageUserExperience). These are returned by GetKeywordsByAdGroupId with ReturnAdditionalFields=QualityScore.",
  "reason": "User asked about keyword quality; only overall QualityScore (1-10) was visible"
}

Related Tools