# Discord App Directory summary names the server job

> Use the 200-character App Directory summary to name the problem your app solves in the server, instead of describing it as a generic bot with features.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/discord-app-directory-summary-names-the-server-job/
- Source: [docs.discord.com](https://docs.discord.com/developers/discovery/best-practices)
- GrowthDex source hub: [Discord Docs: Discovery Best Practices](/sources/discord-docs-discovery-best-practices-docs-discord-com/)
- Last checked: 2026-06-05T05:15:00Z
- Rarity: rare
- Budget: free
- Channels: Communities, SEO, Conversion
- Stages: discord, search snippet, copywriting, app directory
- Key metric: The App Directory Summary field is capped at 200 characters.

## Why this can grow

Discord tells developers to make the Summary field attention-grabbing and problem-led because it is the short line users see in App Directory search results. That changes how the copy should be written. The summary is not a miniature about page. It is closer to a search snippet. Naming the server job to be done gives the buyer a quick reason to click, while vague feature language wastes the tiny amount of attention available in a search result.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. I would treat this as earning the right to be in the room, not dropping a campaign into a room. In community-led growth, the first job is to notice what people already care about, then bring a useful proof, tool, teardown, or question that makes the conversation better. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where discord app directory summary names the server job can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Communities and SEO channel.
3. Use the evidence from docs.discord.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Discord's Discovery Best Practices guide says the App Directory Summary field has a 200-character limit and recommends starting with an attention-grabbing sentence that describes a problem a user wants to solve.

## Adjacent tactics in the same lane

- [Discord App Directory five-asset carousel with best proof first](/growth-ideas/discord-app-directory-five-asset-carousel-with-best-proof-first/) - 2 shared channels, 2 shared stages
- [Slack Marketplace short description in 10 words](/growth-ideas/slack-marketplace-short-description-in-10-words/) - 2 shared channels, 1 shared stage
- [Chrome Web Store summary hook in 132 characters](/growth-ideas/chrome-web-store-summary-hook-in-132-characters/) - 2 shared channels, 1 shared stage
- [Discord App Directory support server tags and language parity](/growth-ideas/discord-app-directory-support-server-tags-and-language-parity/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Discord app page should finish the Add App click](/blog/the-discord-app-page-should-finish-the-add-app-click/) - community-led growth, brand trust, onboarding

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.